4 ms·
When Typescript gets an engine capable of direct competition with JavaScript, then you can claim JavaScript is "dying." Until then, your usage of Typescript is
by msimpson 11y ago
When Typescript gets an engine capable of direct competition with JavaScript, then you can claim JavaScript is "dying." Until then, your usage of Typescript is no different than Objective-C vs. C.
- matthewmacleod 11y agoPretty big goddamn difference there though! That's a little like claiming that essentially every language is the same, because they all end up as machine code.
- msimpson 11y agoC++ and Objective-C both started out as preprocessors of C. So feel free to define the line where a language extension becomes its own independent language. But for me, that line exists where the dependence upon the parent language ends; just as it did with both C++ and Objective-C. At present TypeScript is defined as a superset of JavaScript and is therefore just a broad extension of it. Until its popularity and usage spreads to the point that a full interpreter arrives capable of removing its dependence on JavaScript, it is not a separate language and JavaScript is not "dying." That is my point, and it's not that big of a difference if you understand my historical context. View Dart for more failures of this exact nature.
- awjr 11y agoTypescript just delivers a better quality level of code within a large group of developers.
- msimpson 11y agoNot arguing that in the slightest.