3 ms·

It also has barely seen any activity in years. It is going nowhere. The TC39 committee is utterly dysfunctional and anti-progress, and will not let any this or

It also has barely seen any activity in years. It is going nowhere. The TC39 committee is utterly dysfunctional and anti-progress, and will not let any this or any other new syntax into JavaScript. Records and tuples has just been killed, despite being cited in surveys as a major missing feature[1]. Pattern matching is stuck in stage 1 and hasn't been presented since 2022. Ditto for type annotations and a million other things. Our only hope is if TypeScript finally gives up on the broken TC39 process and starts to implement its own syntax enhancements again. [1] https://2024.stateofjs.com/en-US/usage/#top_currently_missing_from_js https://2024.stateofjs.com/en-US/usage/#top_currently_missin...

johnny22 1y ago
Records and Tuples weren't stopped because of tc39, but rather the engine developers. Read the notes.
- davidmurdoch 1y ago
  Aren't the engine devs all part of the TC39 committee? I know they stopped SIMD in JS because they were mire interested in shipping WASM, and then adding SIMD to it.
  - johnny22 1y ago
    I would say representatives of the engine teams are involved. However not involved enough clearly, because it should have been withdrawn waaay before now due to this issue.
- Osiris 1y ago
  It was also replaced with the Composite proposal, which is similar but not exactly the same.
tkcranny 1y ago
I wouldn’t hold your breath for TypeScript introducing any new supra-JS features. In the old days they did a little bit, but now those features (namely enums) are considered harmful. More specifically, with the (also ironically gummed up in tc39) type syntax [1], and importantly node introducing the --strip-types option [2], TS is only ever going to look more and more like standards compliant JS. [1] https://tc39.es/proposal-type-annotations/ https://tc39.es/proposal-type-annotations/ [2] https://nodejs.org/en/blog/release/v22.6.0 https://nodejs.org/en/blog/release/v22.6.0

johnny22 1y ago

Records and Tuples weren't stopped because of tc39, but rather the engine developers. Read the notes.

davidmurdoch 1y ago
Aren't the engine devs all part of the TC39 committee? I know they stopped SIMD in JS because they were mire interested in shipping WASM, and then adding SIMD to it.
- johnny22 1y ago
  I would say representatives of the engine teams are involved. However not involved enough clearly, because it should have been withdrawn waaay before now due to this issue.
Osiris 1y ago
It was also replaced with the Composite proposal, which is similar but not exactly the same.

tkcranny 1y ago

I wouldn’t hold your breath for TypeScript introducing any new supra-JS features. In the old days they did a little bit, but now those features (namely enums) are considered harmful. More specifically, with the (also ironically gummed up in tc39) type syntax [1], and importantly node introducing the --strip-types option [2], TS is only ever going to look more and more like standards compliant JS. [1] https://tc39.es/proposal-type-annotations/ https://tc39.es/proposal-type-annotations/ [2] https://nodejs.org/en/blog/release/v22.6.0 https://nodejs.org/en/blog/release/v22.6.0