4 ms·
Is that a good reason to write in raw JS today? I'm not betting anything on TypeScript. It was released 11 years ago, and it's incredibly valuable to me. If it
by digging 3y ago
Is that a good reason to write in raw JS today?
I'm not betting anything on TypeScript. It was released 11 years ago, and it's incredibly valuable to me. If it takes another 5 years for ES to implement first-class types, and it's a good implementation, I'll start using ES for new work at that time. What's lost here? TS won't just stop compiling.
- pier25 3y agoI'm not referring to end users like yourself but projects like Deno who have invested a fair amount of resources into supporting TS.
- digging 3y agoOh, yes, that makes more sense. Still, native typing is not even on the horizon for ES, so I think my point stands for businesses that are heavily invested in supporting TS. TS is what we need today, it doesn't make sense to ignore it because theoretically it could be obsolete in 5-10 years.