> Instead they just think it's "that typescript" thing and itgnore it. Iff deno dies it's probably because of that typescript shadow, not despite of it. I don'

> Instead they just think it's "that typescript" thing and itgnore it. Iff deno dies it's probably because of that typescript shadow, not despite of it. I don't know what planet you're living on but this is completely backwards from everything I've seen people say online. > You act as if the typescript compiler and source-maps suddenly stopped working once they're out of the core. I know that I personally don't bother using TS for Node projects until they reach a certain size. I'd love to use it for every tiny script, but the overhead of setting up a tsconfig, figuring out where the build files will go, adding them to the gitignore if there is one, combining the build step and the run step into a little script for development, etc, just tips the equation. On top of that, I can't really ship TS on NPM because that assumes everyone downstream will be willing to do the same config + build process. Deno solves all of this by making TS a first-class citizen. That's huge.