4 ms·
About 95% of React components I see in the wild are in TypeScript. The most rapidly growing JS backend framework (Nest) is in TS. Deno, the evolution of Node, i
by arcturus17 6y ago
About 95% of React components I see in the wild are in TypeScript. The most rapidly growing JS backend framework (Nest) is in TS. Deno, the evolution of Node, is based on TS. Pretty much everything in the JavaScript OSS world has TS options or is based on TS.
I doubt Coffeescript ever saw this scale of adoption.
- pjmlp 6y agoWe only use TypeScript on frameworks that make it a requirement, the language is starting to look like Haskell. As much as I like Anders work, it is impossible to understand modern TypeScript without looking into tsconfig.json before looking into source code.
- zaccusl 6y agoI don't understand what the tsconfig has to do with understanding the source? Maybe when using different path resolving or different tsconfigs to compile test files vs. production files? Many toolings make it so you don't even need to worry about the tsconfig anymore (though in reality it is very helpful to understand it).
- pjmlp 6y agoTo avoid breaking existing source bases, many features or corrections across the language versions are opt-in, so in some projects it looks like GHC feature pragmas.
- madeofpalk 6y agoThis does not align with my experience of writing Typescript at multiple companies of varying sizes and open source projects.
- pjmlp 6y agoLucky you for not having devs that would rather be using Haskell Lens and stuff like that.
- deleted 6y ago[deleted]