3 ms·
> JS/Babel ecosystem I mean, sure. In that when you use typescript you probably don't need/want Babel, as most of the ES6 features you want are part of TS alre
by KirinDave 10y ago
> JS/Babel ecosystem
I mean, sure. In that when you use typescript you probably don't need/want Babel, as most of the ES6 features you want are part of TS already.
> JS ecosystem integration with JSX/whatever.
Typescript supports both react and non-react JSX natively, so perhaps this isn't a pain point anymore?
Also: you get types. Good types are great.
- qwertyuiop924 10y agoWell, yeah, but what about whatever thing comes along in Babel that will make your code an order of magnitude cleaner? What about all the tools that work with babel, rather than TS? And from what I saw, Flow has a type system at least as good as TS's. Am I wrong?
- KirinDave 10y ago> Well, yeah, but what about whatever thing comes along in Babel that will make your code an order of magnitude cleaner? Why not watch http://channel9.msdn.com/Events/Build/2016/B881 http://channel9.msdn.com/Events/Build/2016/B881 and tell me what you think. It sounds to me like they're dedicated not only to being on that, but to be part of the conversation going forward. They're already taking the well-formed parts of the next 2 iterations of JS, and adding types on top. > And from what I saw, Flow has a type system at least as good as TS's. Am I wrong? Flow has a type system that is "as good" at troubleshooting errors within the existing javascript ecosystem, as I read it. And that's good. TypeScript, unlike flow, makes newer features available with the type data.