3 ms·
> While TypeScript is sometimes seen as an improved version of JavaScript, this case is showing that in fact, it’s not. Woah, woah, hold on. This case is showi
by untog 6y ago
> While TypeScript is sometimes seen as an improved version of JavaScript, this case is showing that in fact, it’s not.
Woah, woah, hold on. This case is showing that in the very specific, atypical case the Deno team are using it in, TypeScript is not the right fit.
I’d rather read something that actually interviews the Deno folks about what they are doing, the underlying document is a pretty free ranging discussion and this writeup is making a few assumptions.
- braythwayt 6y agoLawd, the number of times people write an extensive essay detailing how a particular tool didn’t fit their culture, processes, and circumstances, then explain why it’s either irredeemably broken or conversely, that failing to adopt the tool is professional malpractice. N=1. That is all.
- karmakaze 6y agoMay as well drop tests and code reviews if it feels like it's slowing you down. For one-person or very small teams who have full context of a'll changes this can actually work very well. It's with more contributors participating in a mature project that you'd wish these things weren't dropped. Types can be added later so it's not like using php and later wishing you'd used Kotlin.
- karmakaze 6y agoI'll add a datapoint of an analogous case. I updated a legacy java 1.x codebase that was running java 6/7 without generics. Having spent a small amount of effort over a course of months, all the type annotations were updated. It uncovered exactly one bug. The main improvement is for quickly gaining context in unfamiliar code and being able to enable warnings for newly written code without noisy error messages.