3 ms·

Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now

• rrr_oh_man 7mo ago
  Why?
• kitsune1 7mo ago
  The delusion in this comment is insane.
• jitl 7mo ago
  loud people on twitter are always switching to the new hotness. i personally can't see myself using bun until its reputation for segfaults goes away after a few more years of stabilizing. deno seems neat and has been around for longer, but its node compatibility story is still evolving; i'm also giving it another year before i try it.
  • _flux 7mo ago
    Wow, I thought you were exaggerating, but no: https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3Aopen%20segfault https://github.com/oven-sh/bun/issues?q=is%3Aissue%20state%3... Open 80, closed 492.
    • petcat 7mo ago
      That's basically just Zig, right? Re-invented C but only fixed the syntax, not the problems.
      • jitl 7mo ago
        it’s hard to be convinced that zig is an acceptable idea for security critical runtime for web applications.
        • _flux 7mo ago
          And as I understand it, most (if not all) of these segfaults were in casual use, not when someone is trying to attack it..
• dzogchen 7mo ago
  I don't really understand what the value proposition of Bun and Deno is. And I see huge problems with their governance and long-term sustainability. Node.js on the other hand is not owned or controlled by one entity. It is not beholden to the whims of investors or a large corporation. I have contributed to Node.js in the past and I was really impressed by its rock-solid governance model and processes. I think this an under-appreciated feature when evaluating tech options.
  • packetlost 7mo ago
    Deno has some pretty nice unique features like sandboxing that, afaik, don't exist in other runtimes (yet). It's enough of a draw that it's the recommended runtime for projects like yt-dlp: https://github.com/yt-dlp/yt-dlp/issues/14404 https://github.com/yt-dlp/yt-dlp/issues/14404
    • worksonmine 7mo ago
      Node has sandboxing these days: https://nodejs.org/api/permissions.html https://nodejs.org/api/permissions.html
      • dzogchen 7mo ago
        No it doesn't, unfortunately. > The permission model implements a "seat belt" approach, which prevents trusted code from unintentionally changing files or using resources that access has not explicitly been granted to. It does not provide security guarantees in the presence of malicious code. Malicious code can bypass the permission model and execute arbitrary code without the restrictions imposed by the permission model. Deno's permissions model is actually a very nice feature. But it is not very granular so I think you end up just allowing everything a lot of the time. I also think sandboxing is a responsibility of the OS. And lastly, a lot of use cases do not really benefit from it (e.g. server applications).
  • zamadatix 7mo ago
    If one gets nothing from them directly, they've at least been a good kick to get several features into Node. It's almost like neovim was to vim, perhaps to a lesser extent.
• zadikian 7mo ago
  Yes people are using Node.js, most likely the majority.