4 ms·

i’m not sure i buy the “company floods the industry with broken tooling and deserves to be standardized” narrative. yeah, the ecosystem sucks, but rewarding th

i’m not sure i buy the “company floods the industry with broken tooling and deserves to be standardized” narrative. yeah, the ecosystem sucks, but rewarding the system incentivized to co-opt the system will actually make things worse in the long run, not better. for example, internet explorer failed why?

dgellow 2y ago
What broken tooling are you talking about? tsc is broken? IE failed because it was a horrible browser that didn’t evolve for years and was incompatible with major web standard developments. Nothing to do with typescript, an open source, best in class type system and type checker.
- tylerchilds 2y ago
  IE failed because they tried to define the standard as themselves. i argue we’re witnessing that again from the same company that only gave up that strategy once they had typescript, github, npm locked in. i’m not bullish on political strategies being technical solutions, which is the premise. typescript has nothing to do with internet explorer, true, but is it really not obvious that it is the same tactic as a different brand? become the standard, steer the committee. and broken in that copying code between systems requires compatibility between configurations, which should be a red flag for any language.
- tylerchilds 2y ago
  “During the transpilation process, no type checking is performed, and types are discarded.” this node feature is primarily around disregarding typescript in favor of the underlying javascript it represents. that reminds me of this fun article: https://www.richard-towers.com/2023/03/11/typescripting-the-technical-interview.html https://www.richard-towers.com/2023/03/11/typescripting-the-...
  - dgellow 2y ago
    Yes, the feature is about being able to run typescript scripts. It’s not a type checker, it is similar to ts-node, deno, bun, etc. Typescript has been designed for that specific purpose.
    - tylerchilds 2y ago
      seen and heard, my original point was that typescript is not poised to be a tc39 standard. this is still a “runs some typescript” and “not runs every typescript file” “ At least initially in this PR no trasformation is performed, meaning that using Enum, namespaces etc... will not be possible.” this type of nuance is the core of why typescript is a headache for any organization with more than a single codebase— javascript is portable, typescript is in theory, but not in observed practice.

dgellow 2y ago

What broken tooling are you talking about? tsc is broken? IE failed because it was a horrible browser that didn’t evolve for years and was incompatible with major web standard developments. Nothing to do with typescript, an open source, best in class type system and type checker.

tylerchilds 2y ago
IE failed because they tried to define the standard as themselves. i argue we’re witnessing that again from the same company that only gave up that strategy once they had typescript, github, npm locked in. i’m not bullish on political strategies being technical solutions, which is the premise. typescript has nothing to do with internet explorer, true, but is it really not obvious that it is the same tactic as a different brand? become the standard, steer the committee. and broken in that copying code between systems requires compatibility between configurations, which should be a red flag for any language.
tylerchilds 2y ago
“During the transpilation process, no type checking is performed, and types are discarded.” this node feature is primarily around disregarding typescript in favor of the underlying javascript it represents. that reminds me of this fun article: https://www.richard-towers.com/2023/03/11/typescripting-the-technical-interview.html https://www.richard-towers.com/2023/03/11/typescripting-the-...
- dgellow 2y ago
  Yes, the feature is about being able to run typescript scripts. It’s not a type checker, it is similar to ts-node, deno, bun, etc. Typescript has been designed for that specific purpose.
  - tylerchilds 2y ago
    seen and heard, my original point was that typescript is not poised to be a tc39 standard. this is still a “runs some typescript” and “not runs every typescript file” “ At least initially in this PR no trasformation is performed, meaning that using Enum, namespaces etc... will not be possible.” this type of nuance is the core of why typescript is a headache for any organization with more than a single codebase— javascript is portable, typescript is in theory, but not in observed practice.