3 ms·
Under what mechanism would the "extinguish" part be at all possible?
by moron4hire 10y ago
Under what mechanism would the "extinguish" part be at all possible?
- wccrawford 10y agoIt's generally done by having the new "extended" version be so superior that others can't stand using the original anymore.
- moron4hire 10y agoNo, that's not how that works. EEE refers to the times when Microsoft would take an open standard--say HTML, or JavaScript, back when IE3 was actually the best browser on the market--shove in their own, proprietary, backwards-incompatible extensions, and keep calling it the same thing as the open standard. But MS makes it very clear that TypeScript is a different language. It helps a lot that they don't even have the same name, y'know. Also, it's a system for specifically staying backwards compatible with open-standard JavaScript. Using TypeScript does not replace JavaScript. It supplements it.
- nol13 10y agoWhen using TypeScript subtly forces you into a MS toolchain. Then when everyone's hooked on VS Code BAM VS Code Pro Extreme Edition!
- moron4hire 10y agoConsidering VS Code is a light, free alternative to Visual Studio, that scenario is positively absurd.
- spion 10y agoStrangely enough, I'd feel this would be fine. I would pay for a non-free upgrade of VSCode if it really brings in enough value. Its already on par with Sublime, and I paid for that... edit: Though if you mean TypeScript depending on VSCode to build, I doubt thats even possible at this point. Everything is available via the command line. Heck, there are even tools that build on top of the compiler API. (dts-generator, tslint etc)
- nol13 10y agoWell not that it won't compile without VS, but maybe as a vehicle to for the occasional new feature that just doesn't work quite right on Mac, one drive hosted git tie in's, I dunno but their up to something.