4 ms·
I do not particularly like TypeScript because: - It adds complexity and unnecessary dependencies to the project and this makes it more brittle and more difficu
by jondubois 10y ago
I do not particularly like TypeScript because:
- It adds complexity and unnecessary dependencies to the project and this makes it more brittle and more difficult to set up and get running (I often run into issues with it).
- Slows down your debug cycle (it typically takes at least 15 seconds to compile for a small project) so you can't test your assumptions quickly as you would with plain JS - You have to wait all the time and try not to get distracted.
- For an experienced JS developer like me, the vast majority of errors raised by the compiler are pedantic and not related to any real logical flaws - I spend a lot of time catering to the fussiness of the compiler instead of thinking purely about logic.
- Working with legacy JS libraries is a pain.
I will admit though that being able to look up references and usages of various classes and functions without having to leave the IDE is a nice feature - I don't really need it though because I got used to searching through my code with text-matching (sift) and by adhering to a proper source directory structure.
- parent5446 10y agoSurprisingly I have not run into those compile time issues. Maybe it's just my company's own infrastructure, but our TS projects, which can get rather large, all recompile in less than five seconds.
- jondubois 10y agoYeah I'm not sure why it takes so long for me. We're using Angular 2.
- ludicast 10y agoMy compile time is very fast (near instant), but I split up my projects into a zillion private modules. Adds some complexity but great for tdd. TS has been worth it to me, even if once in a while the compiler is too fussy like you say.
- anko 10y agototal side point, but did you know in visual studio code you can enable "editor.codelens" and it will show class references in javascript above the declaration - no typescript required.