home.social

#tc39 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tc39, aggregated by home.social.

  1. 🤣 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. 📧🔄
    inngest.com/blog/hanging-promi #Promise #TC39 #TechHumor #DigitalClutter #ProgrammerLife #HackerNews #ngated

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

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

    #RxJS #Observables #TC39 #ECMA262

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

    #RxJS #Observables #TC39 #ECMA262

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

    #RxJS #Observables #TC39 #ECMA262

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

    #RxJS #Observables #TC39 #ECMA262

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

  8. 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

  9. 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: github.com/tc39/proposal-patte. It says in the readme "Status: Stage 1" (I assume that's not true anymore). So I check the official "proposals" repo (github.com/tc39/proposals), and search for "pattern": Nothing, no results at all. I guess they only track Stage 2.

  10. 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

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

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

    habr.com/ru/companies/otus/art

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

  12. 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?

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

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

    habr.com/ru/companies/timeweb/

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

  14. 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

  15. 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...

  16. #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. mozilla.github.io/standards-po

  17. 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:

    dev.to/this-is-learning/schedu

  18. 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

  19. 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

    developer.mozilla.org/en-US/bl

  20. 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

  21. Is it wrong if I'm kind of enjoying the drama about #ljharb?
    Burn tc39 down! Make the web anew!
    The only standard is death comes to everything!

    #webDev #javaScript #tc39 #nodejs #esm #esmodules #commonjs #cjs #modules

  22. I also moved over my last year’s post on #Reactivity for #WebGPU mighdoll.dev/blog/reactive-web.

    The reactive #signals effort seems to be coming together nicely in #TC39. I’m hoping to revisit the #WebGPU integration to use the current #signals polyfill later this summer.