5 ms·
Big projects are ditching TypeScript why? [video]
- CharlesW 3y agoDHH did drop it because typing was too hard¹: https://world.hey.com/dhh/turbo-8-is-dropping-typescript-70165c01 https://world.hey.com/dhh/turbo-8-is-dropping-typescript-701... As he's notes at https://world.hey.com/dhh/programming-types-and-mindsets-5b8490bc https://world.hey.com/dhh/programming-types-and-mindsets-5b8..., he's just "a dynamic typing kind of guy" and has "embraced the evangelical position for dynamic typing in the past", but is now okay with you using dynamic typing if you want to (as long as you don't work on Basecamp or Hey, presumably). > …TypeScript […] pollutes the code with type gymnastics that add ever so little joy to my development experience, and quite frequently considerable grief. Things that should be easy become hard, and things that are hard become `any`. No thanks! The Svelte example is just clickbait to support an anti-TypeScript narrative. Happily, we have an Actual Explanation by @rich_harris: https://news.ycombinator.com/item?id=35892250 https://news.ycombinator.com/item?id=35892250 ¹ FWIW, I'm a TypeScript newb who learned it doing a PHP to TypeScript conversion and found using types fairly straightforward. ChatGPT and Copilot were helpful when I got stuck or otherwise confused.
- proc0 3y agoFor small codebases, sure. For large ones you want the machine to do the most heavy lifting as much as possible and a type compiler is one more layer in which this can be done. Granted it can also be abused and become a bottleneck, so it's a double edged sword type of tool like most things in software.