2 ms·

I would rather let Typescript evolve a few more years before freezing its development via standardization

suby 2y ago
I'm interested to know what are some things that you (or anyone reading this) feels that Typescript is missing / should change?
- _flux 2y ago
  I don't have a list and I don't even write TS (or do much web dev in general), but I do follow their announcements and it seems every one of them brings new big type things. Nevertheless, I don't see TS support in e.g. browsers being anything useful, as in practice all JS code deployed is already packaged somehow, so the stage to convert TS to JS (and then also checking the types..) fits that just fine. It's useful for hobbyists, but I don't that is a reason enough to come up with a standard.
- rty32 2y ago
  One example: https://github.com/microsoft/TypeScript/issues/30551 https://github.com/microsoft/TypeScript/issues/30551 Which goes to https://github.com/microsoft/TypeScript/issues/9998 https://github.com/microsoft/TypeScript/issues/9998 which captures a lot of such scenarios And just a few releases ago there were some big problems with handling recursive types. I think most are fixed but there may still be a few around. These are things that you run into on a daily basis if you write enough TypeScript. I doubt we should standardize TypeScript before we have definitive solutions to all these. And I 100% agree with the parent's comment.
- low_tech_punk 2y ago
  Maybe it's helpful to analyze TypeScript's track record in deprecating features and creating breaking changes, which could be a big red flag to TC39. I'm all for typing support but my work is mostly prototyping on short lived projects. People maintaining production systems that will eventually become legacy systems might have a different opinion.
pas 2y ago
C++ and Java are quite good at churning out standard docs and new versions every few years. (Even Python is aiming to offer GIL-lessness!)

suby 2y ago

I'm interested to know what are some things that you (or anyone reading this) feels that Typescript is missing / should change?

_flux 2y ago
I don't have a list and I don't even write TS (or do much web dev in general), but I do follow their announcements and it seems every one of them brings new big type things. Nevertheless, I don't see TS support in e.g. browsers being anything useful, as in practice all JS code deployed is already packaged somehow, so the stage to convert TS to JS (and then also checking the types..) fits that just fine. It's useful for hobbyists, but I don't that is a reason enough to come up with a standard.
rty32 2y ago
One example: https://github.com/microsoft/TypeScript/issues/30551 https://github.com/microsoft/TypeScript/issues/30551 Which goes to https://github.com/microsoft/TypeScript/issues/9998 https://github.com/microsoft/TypeScript/issues/9998 which captures a lot of such scenarios And just a few releases ago there were some big problems with handling recursive types. I think most are fixed but there may still be a few around. These are things that you run into on a daily basis if you write enough TypeScript. I doubt we should standardize TypeScript before we have definitive solutions to all these. And I 100% agree with the parent's comment.
low_tech_punk 2y ago
Maybe it's helpful to analyze TypeScript's track record in deprecating features and creating breaking changes, which could be a big red flag to TC39. I'm all for typing support but my work is mostly prototyping on short lived projects. People maintaining production systems that will eventually become legacy systems might have a different opinion.

pas 2y ago

C++ and Java are quite good at churning out standard docs and new versions every few years. (Even Python is aiming to offer GIL-lessness!)