4 ms·
Let's say that tomorrow, Microsoft releases a totally-backwards-incompatible build of Typescript, and starts charging for it. My "way out" of the Typescript ec
by ubertaco 10y ago
Let's say that tomorrow, Microsoft releases a totally-backwards-incompatible build of Typescript, and starts charging for it.
My "way out" of the Typescript ecosystem is:
1.) Change the target to "ES6", and run a compile.
2.) Take those files and use them as my new source files.
3.) Remove Typescript from my build pipeline.
Done. Easiest language migration I've ever done.
- spion 10y agoIts interesting that on one hand, we have this shouting "embrace, extend, extinguish!" directed at TypeScript, and on the other, Facebook with Flow and Babel is doing precisely that: its extending JS with their own type system, adding support for said type annotations to Babel (which is still thought of as the es.next -> es.current compiler) and still calling it JavaScript; or at least, muddying the waters (no extension change). Strangely, it appears to work. I've seen claims that Flow is better because "its just JavaScript, not another language" I don't get it.