5 ms·
In my experience, people who have been experts on JS before TypeScript became a thing hate it. - It doesn't give them any advantages, while severely limiting th
by bakuninsbart 7y ago
In my experience, people who have been experts on JS before TypeScript became a thing hate it. - It doesn't give them any advantages, while severely limiting their options and workflow. For newer developers with background in other languages it is quite nice though.
- gherkinnn 7y agoI understand “limiting options and workflow” as “limiting the stupid amounts of yolo that JS allows”. TS shows you just how bad JS can be without very, very diligent processes to keep it in check.
- jillesvangurp 7y agoFor developers coming from other languages, typescript and the tool support in VS Code is what makes frontend engineering tolerable these days. A big difference with just a few years ago. I insist on it in most projects I'm responsible for. I see no good technical reasons not to use it at this point.
- Aeolun 7y agoI mean, if you really want to, you can configure it to be just JS with .ts file extensions :P
- jillesvangurp 7y agoWell, strict mode is a thing of course. But yes definitely have seen a bit too much code with the any type.
- Zarel 7y agoI was an expert on JS way before TypeScript. I was kind of slow to adopt it because "the type hints are optimized away and can't even be used to boost runtime performance", but when I did start using it, I loved it and wish I had earlier. The linked article says the vast majority love TypeScript, too. I think the real dividing line is probably that people who haven't had to maintain a large project hate TypeScript. (Which is still weird to me, because you can just turn off `no-implicit-any` and get all the benefits without drawbacks.)
- gherkinnn 7y agoGood point. I too only saw the point after being burnt by a large JS application.