3 ms·
Because eventually in a couple of years you can take your ES7 code and remove the transpiration and it will all work seamlessly. Not so much with Typescript.
by Achshar 10y ago
Because eventually in a couple of years you can take your ES7 code and remove the transpiration and it will all work seamlessly. Not so much with Typescript.
- petre 10y agoM$ can achieve world domination again by making the already opensourced Chakra engine run TypeScript directly w/o the need to transpile. Goodbye ES7, hello ES6 soon to be ES7 optionally typed superset.
- sangnoir 10y ago"Not transpiling" sounds like a marginal benefit, considering most apps are going to have a build step anyway.
- vladimir-y 10y agoTranspiling is going to stay, currently you transpile es6/7/typescript=>es5, later you will do es8/9/typescript=>es6/7, and so on, so this point is not relevant.
- Achshar 9y agoI meant it in the code's current state. Suppose the development stops or stagnates in a month or two. The product is complete. So you can remove the transpilation. Also we won't have to transpile current features in the future. That and code can go as is and have the benefit of native execution that it doesn't currently have.