| Yeah. Performance is rarely a concern. Although they are pushing it for serverless where micro benchmarks may matter if they are related to execution and startup time. I think the benefit of deno or bun aren't as obvious when compared in the context of node on DX matter too. Most of the tooling and standard library can be used without using the cli and switching runtime. Tools like tsx simplifies running typescript code directly. It does pretty much what deno does internally using esbuild. The modularity of runtime doesn't matter to consumers even if it's pretty cool. FFI and security features are nice but I think the future is running sensitive code as a wasm module directly in separate isolated context. The browser compatibility is an awesome boost but most bundler will polyfill that for you out of the box and you will use a bundler with either deno or node most of the time. I know polyfilling is not perfect but it's good enough for most. I want to hear what strong reason people have for choosing to use either bun or deno in production. I use deno for writing scripts because it's so easy to run them especially if they have any dependencies but outside of that, I haven't reached out for it. |