Comment on A SvelteKit template for building CMS-free editable websitesparentComments−kevinak3yRich and I chatted a bit about TS vs JSDoc for library authors today on the monthly dev vlog: https://www.youtube.com/live/MJHO6FSioPI?feature=share&t=95TL;DR - Svelte's codebase will move to JSDoc types but still use TS.To be clear - Svelte will still have full support for TS, nothing is changing for users of Svelte.−no_wizard3yWhy adopt the inferior way of declaring types?I just don’t get the issues. TS is great, and generating good types directly from TS is easy with API extractor[0]. It makes it so easy.The resistance to me from the community boggles me and I’m sad Rich feels this way[0]: https://api-extractor.com/−kevinak3yIt's not about generating types though. The reasons are laid out in the video.
Comments
Rich and I chatted a bit about TS vs JSDoc for library authors today on the monthly dev vlog: https://www.youtube.com/live/MJHO6FSioPI?feature=share&t=95
TL;DR - Svelte's codebase will move to JSDoc types but still use TS.
To be clear - Svelte will still have full support for TS, nothing is changing for users of Svelte.
Why adopt the inferior way of declaring types?
I just don’t get the issues. TS is great, and generating good types directly from TS is easy with API extractor[0]. It makes it so easy.
The resistance to me from the community boggles me and I’m sad Rich feels this way
[0]: https://api-extractor.com/
It's not about generating types though. The reasons are laid out in the video.