Node.js needs a virtual file system
blog.platformatic.dev
Node.js needs a virtual file system
1–10 of 275 posts
Re: Node.js needs a virtual file system
#2[dead]
Re: Node.js needs a virtual file system
#3Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
Re: Node.js needs a virtual file system
#4Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
Why?
Re: Node.js needs a virtual file system
#5Would be nice if node packages could be packed up in ZIP files so to avoid the security/metadata tax for small file access on Windows.
Re: Node.js needs a virtual file system
#6>Let me be honest: a PR that size would normally take months of full-time work. This one happened because I built it with Claude Code.
The node.js codebase and standard library has a very high standard of quality, hope that doesn't get washed out by sloppy AI-generated code.
OTOH, Matteo is an excellent engineer and the community owes a lot to him. So I guess the code is solid :).
Re: Node.js needs a virtual file system
#7Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
The delusion in this comment is insane.
Re: Node.js needs a virtual file system
#8Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
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.
Re: Node.js needs a virtual file system
#9Are people still building new projects on Node.js? I would have thought the ecosystem was moving to deno or bun now
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.
Re: Node.js needs a virtual file system
#10Most of the 4 justifications mentioned sound like mitigations of otherwise bad design decisions. JavaScript in the browser went down this path for the longest time where new standards were introduced only to solve for stupid people instead of actually introducing new capabilities that were otherwise unachievable.
I do see some original benefits to a VFS though, bad application decisions aside, but they are exceedingly minor.
As an aside I think JavaScript would benefit from an in-memory database. This would be more of language enhancement than a Node.js enhancement. Imagine the extended application capabilities of an object/array store native to the language that takes queries using JS logic to return one or more objects/records. No SQL language and no third party databases for stuff that you don't want to keep in offline storage on a disk.