13 comments

[ 2.9 ms ] story [ 39.5 ms ] thread
Forgive me, but it's not clear what this actually does.

Is it a map that commits to disk? Does it operate on the filesystem level, or talk to the raw partition directly (as sort of suggested by the example)? What's it for?

>1000 lines of code in one file. Can't get a good sense of what it does, either.
It uses the standard Node.js filesystem functions. Set a key a value writes the value to a file defined by the key and the name of the map that you set when you create it.

I have no idea what it's for.

(comment deleted)
How is it different from something like node localstorage ?
No offense, but if some code/library/project has no proper README and documentation, I immediately dismiss it as a potential candidate for use in any of my projects.

It is unclear to me what this even is and why I possibly should want to use it.

Seeing the caveats:

> - very slow

> - inefficient

> - incomplete

> - buggy and leaky

I'm assuming it isn't intended for production use, at least right now, maybe ever. Could just be early, could be a toy project, could even be satirical.

It is AGPL, so if you use it, even internally, you basically open sourced your whole application.
What's the purpose of this ? Where it would be useful for ?
So you know, this is neither satire, nor a toy. I made this, a serious project.