Why are some big open-source projects like Turbo and Svelte dropping TypeScript in favor of vanilla JavaScript? Learn about the pros and cons of TypeScript#p...
I wonder how Svelte’s code is built to make this tradeoff worth it. I’ve been using TS for a long time and in every project the compilation part was the shortest task in the whole build process, especially when you compare it with bundling or running unit tests.
If that’s what this video is about then it’s a lie (I’m not going to watch that bait). Svelte did not move away from Typescript. Svelte just moved from TSs custom syntax to TS-in-JSDoc. They are still using the same types and TS compiler to fully enforce type checking their code.
Their reason isn’t that TS is bad, just that the IDE experience is bad redirecting you to .d.ts instead of source files for libraries.
I wonder how Svelte’s code is built to make this tradeoff worth it. I’ve been using TS for a long time and in every project the compilation part was the shortest task in the whole build process, especially when you compare it with bundling or running unit tests.
If that’s what this video is about then it’s a lie (I’m not going to watch that bait). Svelte did not move away from Typescript. Svelte just moved from TSs custom syntax to TS-in-JSDoc. They are still using the same types and TS compiler to fully enforce type checking their code.
Their reason isn’t that TS is bad, just that the IDE experience is bad redirecting you to .d.ts instead of source files for libraries.
Afaik it had more to do with another layer of abstraction then with compike time.