4 ms·
No, JavaScript being the kind of language that requires 3rd parties to implement what should be core features is what creates fragmentation. There was similar
by ryandvm 6y ago
No, JavaScript being the kind of language that requires 3rd parties to implement what should be core features is what creates fragmentation.
There was similar fragmentation with JavaScript's async patterns. Callbacks, promises, async/await also resulted in fragmentation as you had different projects supporting different patterns as 3rd parties introduced new capabilities (that eventually graduated into fully-fledged language features).
Hopefully the best of what TypeScript provides will make its way into the ECMAScript spec eventually...
- danShumway 6y agoAgreed. And importantly, the fragmentation of the Javacript ecosystem is on purpose: https://github.com/extensibleweb/manifesto https://github.com/extensibleweb/manifesto I think about the fragmentation that shows up in the form of multiple frameworks and patterns as a necessary part of that. It's not something that I want to fix. So to draw a line and say, "extending core Javascript features is fine, but compiling into Javascript isn't" -- I just don't get that. Typescript is a testing ground not just for typed programming in general, but also for features like decorators and meta-programming features. It's good to have a diversity in what people are building and using, that's how we get real world data on what works.
- oaiey 6y agoYou forgot observables :)