4 ms·
Typescript seriously needs to start getting its act together. The roadmap shows they're making some headway on these new es6 features, but it feels like they're
by nothrabannosir 12y ago
Typescript seriously needs to start getting its act together. The roadmap shows they're making some headway on these new es6 features, but it feels like they're trying to both accept it for es6 output mode, and for es3/es5 output mode. This means further delays, during which period we can't use them at all.
And because typescript != javascript, we can't use any other tools, either. TS is duplicating the 6to5 efforts, with little to show for it.
If you use TS, right now you're stuck with es5. It's starting to itch.
I wish they'd prioritize the es6 features in es6 output mode and let me worry about converting that to es5.
- aikah 12y agoIt gets worse when someone tries to use Typescript AND JSX in the same project. A total hell since both languages are incompatible.
- TheAceOfHearts 12y agoWouldn't it make more sense to go with JSX and Flow?
- antihero 12y agoFrankly, I don't see why they don't do something like compiling purely to ES6 and then having the transpiling to ES6 handled by something like Babel.
- nwah1 12y agoPretty sure that's the plan.
- mixonic 12y agoInternally TS is a two pass compilation. First type check, then transpile to ES5. The type check step should be available to run on its own. IMO they should not even worry about transpiling, just be a type checking engine. The API for TS, last I used it, was extremely limited. It has always been viewed as a black box compiler by the authors- they need to expose more flexibility.