> the first thing any project is going to do is enable all of that I'm sure many (most) will but the point is that for those who do care about security, Deno o

> the first thing any project is going to do is enable all of that I'm sure many (most) will but the point is that for those who do care about security, Deno offers them the option of running their server app with such features selectively enabled according to need. > it's coupled to Microsoft's take on Javascript Deno supports Javascript too so there's no tight coupling here. It's also a second well-supported widely-used independent implementation of microsoft's syntax, which is no hard guarantee of anything but bodes well if vendor lock-in is a concern. > What about Flow Flow is significantly less popular so this decision seems understandable. I cannot see Deno being as popular as it is now if they had opted for Flow. Also, while Flow has some advantages, it's a lot less expressive and most reviews of both prefer TS for quite well-argued objective reasons. > What's wrong with using Babel with sourcemaps? Given the complaint about coupling just two sentences previous to this one, this makes your comment seem quite disingenuous. Are you serious??? > Will that not just bring about another npm situation in a few years? It might but your goalposts seem to be moving. Are you saying this makes it worse than npm somehow?