> Deno is a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.<p>Still don’t fully understand what ‘runtime’ means in this context. It’s not the parser, interpreter, VM, GC I think, because that is the V8 part. It’s not a runtime compiled into an executable like Haskell or Go.<p>Is it the term used here for a set of standard libraries? Or maybe in interaction layer with the operating system underneath, or the package/build system? Or an umbrella term for all of this?<p>I’ve been doing all kinds of JavaScript and TypeScript for a long time now without a runtime (I think) so pretty curious.
Has anyone played with both Deno and Bun? They seem very similar but while Deno uses V8 (like Node), Bun uses Apple's JavaScriptCore.<p><a href="https://bun.sh/" rel="nofollow noreferrer">https://bun.sh/</a><p><a href="https://deno.com/" rel="nofollow noreferrer">https://deno.com/</a>
I've enjoyed trying to use Deno for a small new service at $WORK. Sadly had to give up and retreat back to Node due to missing support for private NPM repositories and lack of Datadog tracing support.<p>Their compatibility is getting better and better, so I'm confident Deno will eventually be a clear "better Node".
Deno is great. I wish the maintainers were open to moving some of the great functionality from the CLI into separate libraries, but I understand how that might not be desirable from business perspective.
Tangentially related: what is the benefit of Deno KV over something like S3? I see option for atomic transaction, which is nice, but otherwise fewer features for far higher cost. Is it mostly speed?