Re:Turbo 8 is dropping TypeScript
by LudwigNagasena on Thursday September 07, 2023 @03:14AM
(#37415691)
> places where JS makes more sense (eg libraries that would otherwise need to have very abstract types)
If your library is hard to type, it is a code smell. In my opinion, such libraries could benefit from TS a lot.
libraries if they are popular in general are expected to work with a wide variety of code. Supporting code smell is a feature.
variety of code is one thing, your library can be used in thousands of places, doesn't mean it have to do thousands of different things
Re:Turbo 8 is dropping TypeScript
by seattle_spring on Friday September 08, 2023 @10:54AM
(#37434285)
Can you share some examples of libraries you feel benefit from this sort of unlimited flexibility?
Re:Turbo 8 is dropping TypeScript
by PH95VuimJjqBqy on Monday September 11, 2023 @05:09AM
(#37464688)
jquery
I don't think the dichotomy exists because the TS ecosystem is autonomous. You can use TS with any JS library through type declarations and the definitely typed repo. What the js community thinks about typescript honestly doesn't matter. The only practical difference it makes for me is having to do `npm add @types/{library_name}`
I'd understand opting for either JS or TS as a policy going forward, but it's hilarious that this dude probably worked himself up so intensely about this that he brazenly rug-pulled his own repo and invalidated all open PRs.