4 ms·
I'm drinking the TypeScript Kool Aid right now and I'm still not convinced. Ill give it a chance, since I'm still early in the project. The good: it uses a str
by k__ 10y ago
I'm drinking the TypeScript Kool Aid right now and I'm still not convinced. Ill give it a chance, since I'm still early in the project.
The good: it uses a structural type system. For someone who got the good old 'JavaScript is a toy language you should try Java or C#' at university, this feels really refreshing. It mostly works as JS and you get some nice auto complete. So it feels dynamic and not clunky, like the aforementioned 2 'true' languages.
The bad: the tools seem to work random. Sometimes they pick up the definitions, next time you open a file, 'cannot find module 'react'' or numbers in import paths break the auto complete etc. also often you don't find type definitions for you libs and as a type-n00b you often lack the skills to create good ones yourself.
Anyway, I hope with TS 2.0 things will get better. Especially with strict null checks, which hopefully will be a giant win.