3 ms·

You're making a fine argument, but you assume things freeze in time. Whether or not TS will stick to ECMA script in the future is speculation. A similar argume

You're making a fine argument, but you assume things freeze in time. Whether or not TS will stick to ECMA script in the future is speculation. A similar argument to yours could be made where we speculated that JS introduces a typing system in the future and hence creates an incompatibility (to .e.g. TS), hence TS is bad. But I've specifically not tried to speculate in the post. I value that the two languages are very similar and that TS respects ECMA script. However, my argument was (whether you think it was misguided by that silly Objective-C example or not) that TS and JS are different by equality and identity (current and potentially for the future), which is why they belong in different package managers.

virtue3 6y ago
Except its directly trended towards being like JS. It was slightly divergent at some point. (see other commends under my original). Your reasoning is unsound. I'm sorry. https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals#goals https://github.com/microsoft/TypeScript/wiki/TypeScript-Desi... Please see goal number 6. Typescript is an opensource language (probably in mostly control of MS. but they are a -very- different company from even 10 years ago). I can tell you from the last few years that they are taking it very very seriously. Now that ES is actually moving again, no one wants a repeat of coffeescript. Your argument is basically also saying that JSX/React are bad as well and should not be in npm either. I don't think any npm package owes it to anyone to be in any language. They are just under the contract of producing javascript that is runnable under the node versions they've specified (and even then, not even, as there are plenty of browser-only packages). There are plenty of npm modules that have some sort of compilation from C or some such. (anything with node-gyp). Not as common as in ruby land but still happens.

virtue3 6y ago

Except its directly trended towards being like JS. It was slightly divergent at some point. (see other commends under my original). Your reasoning is unsound. I'm sorry. https://github.com/microsoft/TypeScript/wiki/TypeScript-Design-Goals#goals https://github.com/microsoft/TypeScript/wiki/TypeScript-Desi... Please see goal number 6. Typescript is an opensource language (probably in mostly control of MS. but they are a -very- different company from even 10 years ago). I can tell you from the last few years that they are taking it very very seriously. Now that ES is actually moving again, no one wants a repeat of coffeescript. Your argument is basically also saying that JSX/React are bad as well and should not be in npm either. I don't think any npm package owes it to anyone to be in any language. They are just under the contract of producing javascript that is runnable under the node versions they've specified (and even then, not even, as there are plenty of browser-only packages). There are plenty of npm modules that have some sort of compilation from C or some such. (anything with node-gyp). Not as common as in ruby land but still happens.