#tc39 — Public Fediverse posts

🤣 Ah, the elusive quest to cancel a #JavaScript promise—like trying to "unsubscribe" from those pesky emails, except sometimes a mysterious force lets you do it. 🤦‍♂️ TC39's valiant crusade for #cancellation ended in a Shakespearean tragedy of "to cancel, or not to cancel." Spoiler: you're still stuck with dangling promises and digital clutter. 📧🔄
https://www.inngest.com/blog/hanging-promises-for-control-flow #Promise #TC39 #TechHumor #DigitalClutter #ProgrammerLife #HackerNews #ngated

🤣 Ah, the elusive quest to cancel a #JavaScript promise—like trying to "unsubscribe" from those pesky emails, except sometimes a mysterious force lets you do it. 🤦‍♂️ TC39's valiant crusade for #cancellation ended in a Shakespearean tragedy of "to cancel, or not to cancel." Spoiler: you're still stuck with dangling promises and digital clutter. 📧🔄
https://www.inngest.com/blog/hanging-promises-for-control-flow #Promise #TC39 #TechHumor #DigitalClutter #ProgrammerLife #HackerNews #ngated

I feel like the currently-proposed TC39 Observables lacking some value that can be supplied upon "completion" is a mistake. #RxJS #Observables #TC39 #ECMA262

I feel like the currently-proposed TC39 Observables lacking some value that can be supplied upon "completion" is a mistake.

#RxJS #Observables #TC39 #ECMA262

I feel like the currently-proposed TC39 Observables lacking some value that can be supplied upon "completion" is a mistake.

#RxJS #Observables #TC39 #ECMA262

Am I the only one to think that it's good that cancellable promises never made it into any specs whatsoever?

#JavaScript #ECMAScript #ECMA262 #TC39

Am I the only one to think that it's good that cancellable promises never made it into any specs whatsoever?

#JavaScript #ECMAScript #ECMA262 #TC39

Getting information about the status of #TC39 proposals is a horrible process: As a developer, I want to know how far along the "Pattern matching" feature is.

So I google "TC39 Pattern Matching". First result is this GitHub repo: https://github.com/tc39/proposal-pattern-matching. It says in the readme "Status: Stage 1" (I assume that's not true anymore). So I check the official "proposals" repo (https://github.com/tc39/proposals), and search for "pattern": Nothing, no results at all. I guess they only track Stage 2.

Getting information about the status of #TC39 proposals is a horrible process: As a developer, I want to know how far along the "Pattern matching" feature is.

So I google "TC39 Pattern Matching". First result is this GitHub repo: https://github.com/tc39/proposal-pattern-matching. It says in the readme "Status: Stage 1" (I assume that's not true anymore). So I check the official "proposals" repo (https://github.com/tc39/proposals), and search for "pattern": Nothing, no results at all. I guess they only track Stage 2.

Every so often I get an email notification from some starred bug report about TC39 decorators, and I peek at what's going on, and it seems like the current situation is that it's fully standardized but all 3 browsers went "This is complicated and we don't feel like implementing it" 😞

#JavaScript #Decorators #TC39

Every so often I get an email notification from some starred bug report about TC39 decorators, and I peek at what's going on, and it seems like the current situation is that it's fully standardized but all 3 browsers went "This is complicated and we don't feel like implementing it" 😞

#JavaScript #Decorators #TC39

Promise.try: единый вход для sync/async и единая обработка ошибок

Привет, Хабр! Не раз ловил себя на том, как в код-ревью всплывает одна и та же проблема: часть наших функций синхронные, часть асинхронные, а часть ведут себя как шрёдингеровские коты и делают вид, что синхронны, пока не дотронешься. В итоге в одном месте у нас try/catch, в другом .catch , где-то внезапно падает исключение, а в соседнем модуле молча утекает Promise. С появлением нативного Promise.try стало проще навести порядок и избавиться от разнобоя. Фича прошла процесс стандартизации в TC39 и включена в спецификацию ECMAScript 2026, при этом уже с января доступна в актуальных движках. Можно перестать спорить про обёртку из Promise.resolve().then и получить единый вход для sync/async с нормальной обработкой ошибок.

https://habr.com/ru/companies/otus/articles/940298/

#js #Promisetry #JavaScript #ECMAScript_2026 #TC39 #синхронный_код #асинхронный_код

I'm working on a #poc in plain #nodejs 👀
Not published yet, put maybe I will fight #nestjs as a competitor 🤔

This is already working AND fully written in #es2025 #esm with #tc39 decorator proposal

What do you think?

I'm working on a #poc in plain #nodejs 👀
Not published yet, put maybe I will fight #nestjs as a competitor 🤔

This is already working AND fully written in #es2025 #esm with #tc39 decorator proposal

What do you think?

[Перевод] Будущее JavaScript: что нас ждет

Недавно прошла 108-я встреча TC39, на которой было продвинуто 9 предложений на разные стадии стандартизации — от сырых идей (Стадия 0) до полностью утвержденных возможностей (Стадия 4). Ниже краткий обзор этих предложений и того, что они могут привнести в JavaScript.

https://habr.com/ru/companies/timeweb/articles/927768/

#javascript #js #tc39 #ecmascript #future #proposal #будущее #предложение #standart #timeweb_статьи

Two of the nicest new #JavaScript features of recent times:

Iterator Helpers (`.values()`) and `Array.fromAsync()`

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator#iterator_helper_methods

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/fromAsync

#ecma262 #tc39 #mdn #ecmascript #webdev #webdevelopment

Two of the nicest new #JavaScript features of recent times:

Iterator Helpers (`.values()`) and `Array.fromAsync()`

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Iterator#iterator_helper_methods

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/fromAsync

#ecma262 #tc39 #mdn #ecmascript #webdev #webdevelopment

#Development #Overviews
When can I use the Temporal API? · Why JavaScript’s Date API replacement took so long https://ilo.im/165c7r

_____
#TC39 #EcmaScript #JavaScript #TemporalAPI #DateAPI #API #Browser #WebDev #Frontend

#Development #Overviews
When can I use the Temporal API? · Why JavaScript’s Date API replacement took so long https://ilo.im/165c7r

_____
#TC39 #EcmaScript #JavaScript #TemporalAPI #DateAPI #API #Browser #WebDev #Frontend

Ooh Math.clamp would be cool, one less helper I need to keep rewritting https://github.com/tc39/proposal-math-clamp

#Notes #JavaScript #TC39

#Development #Proposals
TC39 advances 9 JavaScript proposals · Three features are ready to join ECMAScript https://ilo.im/164is3

_____
#TC39 #EcmaScript #JavaScript #WebDev #Frontend #Backend

#Development #Proposals
TC39 advances 9 JavaScript proposals · Three features are ready to join ECMAScript https://ilo.im/164is3

_____
#TC39 #EcmaScript #JavaScript #WebDev #Frontend #Backend

I'm gonna settle it once and for all:

the tc39 should adopt the F# style for pipeline operator.

No questions asked.

#FunctionalProgramming #JavaScript #TC39 #ECMAScript #ECMA262 #FP #PipelineOperator

I'm gonna settle it once and for all:

the tc39 should adopt the F# style for pipeline operator.

No questions asked.

#FunctionalProgramming #JavaScript #TC39 #ECMAScript #ECMA262 #FP #PipelineOperator

During tonight's AmsterdamJS #Meetup Special Edition with #TC39 Members (1800 CET), I will share the history of the #JavaScript Decorators proposal, which is now in Stage 3 of Ecma TC39's standardization process www.meetup.com/amsterdamjs/...

AmsterdamJS Special Edition: A...

#Mozilla Standards Positions. This page tracks Mozilla's positions on open Web and Web-related specifications submitted to standards bodies like the #IETF, #W3C, #WHATWG, and #Ecma #TC39. Please remember, this isn't a commitment to implement or participate; it's just what we think right now. See dev-platform to find out what we're implementing. https://mozilla.github.io/standards-positions/

#Development #Proposals
TC39 advances a few JavaScript proposals · Three features are ready to join ECMAScript https://ilo.im/162h89

_____
#TC39 #EcmaScript #JavaScript #WebDev #Frontend #Backend

#Development #Proposals
TC39 advances a few JavaScript proposals · Three features are ready to join ECMAScript https://ilo.im/162h89

_____
#TC39 #EcmaScript #JavaScript #WebDev #Frontend #Backend

Highly recommended article by @ryancarniato on #JavaScript Signals and scheduling of async funcs.

I had my own share of problems (in Lit) with the #TC39-#Signal proposal, but failed to blog about it so far. Glad others recognize it could be too early to standardize…

Scheduling Derivations in #Reactivity:

https://dev.to/this-is-learning/scheduling-derivations-in-reactivity-4687

Highly recommended article by @ryancarniato on #JavaScript Signals and scheduling of async funcs.

I had my own share of problems (in Lit) with the #TC39-#Signal proposal, but failed to blog about it so far. Glad others recognize it could be too early to standardize…

Scheduling Derivations in #Reactivity:

https://dev.to/this-is-learning/scheduling-derivations-in-reactivity-4687

Anybody on #TC39 want to champion an ECMAScript proposal? Before I write a whole explainer document I’d like to make sure it isn’t wasted effort.

In short: Symbol.call, a well-known symbol, which can be used as a method name to make an object callable. Prior art: #Ruby’s call(), E’s run (), C++’s operator(). Allows your class’s instance to act as a Functor Object, and eases use of Method Object pattern. Gives us a way to make callables have their own “this.”

#JavaScript #JS #WebDev

Anybody on #TC39 want to champion an ECMAScript proposal? Before I write a whole explainer document I’d like to make sure it isn’t wasted effort.

In short: Symbol.call, a well-known symbol, which can be used as a method name to make an object callable. Prior art: #Ruby’s call(), E’s run (), C++’s operator(). Allows your class’s instance to act as a Functor Object, and eases use of Method Object pattern. Gives us a way to make callables have their own “this.”

#JavaScript #JS #WebDev

Twice a year, due to a very old system, many assumptions, user expectations, and a bright mind that decided to set a database in Europe/Amsterdam TZ, we have to deal with at least a bug regarding time issues. I cannot wait for Temporal to be fully implemented in all the platforms.

#javascript #temporal #tc39

https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/

Twice a year, due to a very old system, many assumptions, user expectations, and a bright mind that decided to set a database in Europe/Amsterdam TZ, we have to deal with at least a bug regarding time issues. I cannot wait for Temporal to be fully implemented in all the platforms.

#javascript #temporal #tc39

https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/

Just noticed this #js behaviour found it interesting/surprising

```javascript
let o = {}
let i = 0;
o?.f?.(i++)
```

The value of `i` is `0` after this expression. I would have thought that the orders of evaluation would still lead to `i++` occurring even if the method call is short circuited. But `i++` never evaluates.

#js #javascript #tc39 #webdev

Just noticed this #js behaviour found it interesting/surprising

```javascript
let o = {}
let i = 0;
o?.f?.(i++)
```

The value of `i` is `0` after this expression. I would have thought that the orders of evaluation would still lead to `i++` occurring even if the method call is short circuited. But `i++` never evaluates.

#js #javascript #tc39 #webdev

Updates from the TC39 meeting in December 2024
@gnumanth
https://dev.to/hemanth/updates-from-the-105th-tc39-meeting-3gkh

#ECMAScript #JavaScript #TC39

Updates from the TC39 meeting in December 2024
@gnumanth
https://dev.to/hemanth/updates-from-the-105th-tc39-meeting-3gkh

#ECMAScript #JavaScript #TC39

TC39 advances 10+ ECMAScript proposals
@sarahgooding @SocketSecurity
https://socket.dev/blog/tc39-advances-10-ecmascript-proposals-key-features-to-watch

#ECMAScript #JavaScript #TC39

TC39 advances 10+ ECMAScript proposals
@sarahgooding @SocketSecurity
https://socket.dev/blog/tc39-advances-10-ecmascript-proposals-key-features-to-watch

#ECMAScript #JavaScript #TC39

#Development #Outlooks
TC39 advances 10+ ECMAScript proposals · Prominent JavaScript features to keep an eye on https://ilo.im/160e65

#Proposals #TC39 #ECMAScript #JavaScript #Browser #WebDev #Frontend

#Development #Outlooks
TC39 advances 10+ ECMAScript proposals · Prominent JavaScript features to keep an eye on https://ilo.im/160e65

#Proposals #TC39 #ECMAScript #JavaScript #Browser #WebDev #Frontend

The "on-topic" channel has now lost all relation to the topic #tc39

OH at plenary “if people would stop using the word orthogonality, that would be great” #TC39

The overall cognitive capacity of TC39 delegates is reflective of the last hour or two of the final day, day three. the off-topic channel has completely gone off the rails, and the on-topic channel is just barely hanging on. Contributions are constructive yet somehow also unhinged.

we're halfway through day two.

#tc39

From the agenda for the 104th meeting of Ecma #TC39 (https://github.com/tc39/agendas/blob/main/2024/10.md#agenda-items). Longer or open-ended discussions: JSSugar/JS0: https://docs.google.com/presentation/d/1ylROTu3N6MyHzNzWJXQAc7Bo1O0FHO3lNKfQMfPOA4o/mobilepresent?slide=id.g30432c5cd9c_0_688. Slide 40 onward 👀:

Let's standardize as the ecosystem uses it:

JS0: the language implemented by the engines

JSSugar: features that must be compiled by tools to JS0

For developers, JS = #JS0 + #JSSugar

If #tc39 could finally get approved and supported by #javascript in the #browser -- that'd be great, mkay? #webdev #programming