4 ms·
> That is a valid point, but honestly, avoiding (learning) TypeScript as a modern day JavaScript developer is a mistake. You're probably right. My argument, ho
by timdaub 6y ago
> That is a valid point, but honestly, avoiding (learning) TypeScript as a modern day JavaScript developer is a mistake.
You're probably right. My argument, however, was purely about separation of concerns: different language means different package manager (or namespace...).
- oaiey 6y agoI disagree. Node and the browsers script engines are virtual machines nowadays. Package managers go by VMs not by language.
- timdaub 6y agoNot sure I get your argument. As far as I understand there's no VM for Typescript specifically. Hence as "no VM" is different from Spidermonkey/V8, Typescript packages should go into its own package manager?
- virtue3 6y agoA kotlin project is going to use both java and kotlin sources (and maybe closure). We're going to start seeing a lot more WASM stuff on npm, which is going to be whatever language anyone wants. The VM for typescript is node/browser. Because it gets compiled to target those.