BrowserFS: An in-browser filesystem supports various back ends

In general, projects like these are great — they unify a lot of underlying architecture and, with time, can make them ubiquitous to use. LocalForage[1] is a great example of this, and I would recommend using that over regular local storage for every serious web project. This project raises my eyebrows at two technical points, though: There is no mention of "Promise" or "async/await" in the readme. I know the project tries to mirror the current Node filesystem, but that…

I'm a huge fan of the work here & strongly strongly believe in file-system oriented architectures. Being able to use a wide number of existing "server side" libraries in the browser could be a huge win. And this has interesting server side applications too, where one can use the same Node.js code but target diverse & interesting backends & overlayed systems. Having a virtual-fs is an incredibly powerful and useful concept. "Everything is a file!" still sounds like a great…