My Emacs came with a good text editor out of the box. If yours doesn't you may have one of those terrible configurations which uses Evil.

It has wayyyyy better nodejs compatibility (day 1 goal)

As far as I know, modern Node compat in Deno is also quite great - I just import packages via 'npm:package' and they work, even install scripts work. Although I remember that in the past Deno's Node compat was worse, yes.

Pretty sure one of the Deno day 1 goals was to correct mistakes made during the early days of Node.js.

Opened it, saw I needed to wrap my routes with api(), closed it - sounds like a solution for a problem PaaS has solved 10 years ago.

Deno is just a marketing company dressed as a software startup

And Rust is the perfect lingua franca to accomplish this.

The demise of both of these trends cannot come soon enough.

> Deno is written in Rust, which allows them to move faster and more safely. Contributing to and extending Deno is a breeze. You can add Rust crates to the runtime and use them from JS.

Most of Deno's code is actually V8 in C++

Github actually has this feature (only for open source and enterprise IIRC) when there is a SARIF output

SARIF output is on our Roadmap btw!

Github code scanning is not so great from what we've heard so far, but also it's very expensive, you need to be on the Enterprise plan...

It took a friend and I 2 days last year to build a compatibility layer that allowed to run all the tests of Deno on Node.

Ryan: let's use web standards Also Ryan: let's use TSX lol

PRs on doc are always appreciated.

> Could you not just build a URL loader and cache for importing in Node.js? Could sandboxing not just be a flag in Node.js? Do you really need TypeScript built in?

There are open PRs on node for the first two parts ^^ It's 100% doable.

Seems like Deno will have some great competition then. I'd rather slowly implement such functionality than dump everything.