I'm curious why NeDB wouldn't suffice.

https://github.com/louischatriot/nedb

From the slideshare presentation on the homepage (p. 4)[1]

> Performs better than similar products (NeDB, TaffyDB, PouchDB etc.) and it's much smaller

It would be interesting to see benchmarks.

[1] http://www.slideshare.net/techfort/lokijs/4

Ok, TaffyDB is a piece of crap. You call `.fetch` to fetch a document at some id, but if you modify your fetched copy, the copy in the database is also modified. With a database like this I'm much better with a hashmap.

there is this benchmark : https://github.com/danstocker/jorder/wiki/Benchmarks ... I maintain this one (https://github.com/kristopolous/db.js) which is part of that.

From my perspective, with a small collection size, I'll sacrifice performance for expressiveness. I have a number of expensive features that I think do nice things.

Thanks for sharing that. I jumped the gun before commenting.

No worries. I just noticed they include the benchmarks here [1]

[1] https://github.com/techfort/LokiJS/tree/master/benchmark

I've iterated twice on these kinds of projects. First was Drywall and the latest is Frame. Drywall includes a front-end and Frame is just an API. Finding a happy medium of features is tricky. Some choices limit your audience quite a bit.

Drywall [https://github.com/jedireza/drywall] Drywall is limited to people who're ok using Grunt instead of Gulp or Backbone instead of _______, etc...

Frame [https://github.com/jedireza/frame] I created Frame to appeal to a larger audience. And because all the front-end opinions were removed it plays nicer since you "bring your own front-end". Interestingly enough, now I'd like to provide Postgres as well as Mongo db connections.

In general these projects are interesting and I think serve best as examples of apps beyond the absolute basics. Once you make an app yours, it'll probably go in it's own direction quickly.

Hey HN. Developer here.

This is the second iteration of creating a user system boilerplate/kit. The first was Drywall which you can find on my GitHub page. I'd love to know what you like and what sucks.

I find it interesting that there is little to no conversation about the integration with git. In one of the the screenshots I saw a branch name and icon in the bottom status bar. I assume this is an important motivation for GitHub.

Wow. nodestreams.com is great. It's really helpful to see the results of different chained combinations instantly. Thanks for making this John.

This is exactly what Drywall was designed for. It's a website and user system for Node.js

Feedback is welcomed.

http://jedireza.github.io/drywall/

Edit: more so for a functional side project, not a static website.

I am a dev with C background and zero experience in nodejs. I have been using Drywall to get a Web GUI frontend for a CLI tool. Progress are slow on my side, yet it was very helpful to get me started.

Looks good. Thanks.

Drywall - A website and user system for Node.js http://jedireza.github.io/drywall/

Recent cool news: got word from the hosts of Node Knockout that submissions are allowed to use it in the competition.

I'm happy to hear this. It was nice of Bjørn to build the node API in the first place. It's great that this became the official API, congrats all around.

Just curious, would the original author be compensated for this? How does that work?

I wrote the package because I needed it. My compensation came when my package worked and I could use it. Since then it was just a "cost" because I chose to maintain it for the community. Like most of us I write software for money, too, but in this case the stripe package was just "collateral benefit" from something else I was doing.

I didn't have time to do the cleanups and rewrite that the package deserved to get support for the new Stripe features with a consistent API.

I haven't been needing the new features myself, so honestly I was delighted when they asked months ago if they could take it over. For them and for the community it was better this way than if they'd just forked it or just published another package.

Thanks for your open source contribution, it's been a big help.

Very cool! Great work and thank you for your insight.

Typically I wouldn't think so because there is an F in FOSS, after all. However, they explicitly say that they worked with him, so I would imagine it was paid time.

Disclaimer: I have no connection to Stripe (aside from wishing I had gotten pc's username first!) so I'm just guessing.

This is the same stack that Drywall is built with. When you're ready to get past a simple hello world app, please take some time to checkout the project.

http://jedireza.github.io/drywall/

Care to give elevator pitch for drywall? I checked it out and looks interesting, but wanted to see where you were going with it.

Hey Jason, thanks for taking a look. Right now it's just an open source project of mine, not a business or anything. If something isn't clear after reading the GitHub page, please open an issue or send me an email. I've started breaking out wiki pages from questions I've received. My main focus right now is getting more eyes on the project and gathering feedback.

Since I've built user/admin systems for the majority of my career, this is really interesting to me. The site looks great and the Family Guy stuff is funny ("No,n0_p4ssword!") Hah.

I agree with the lion share of what WA said.

The MVP/prototype argument is a valid one, but remembering that nothing lasts forever, it's probably wise to think of these services as temporary tools and not permanent solutions.

I believe that user management is such an important (and basic) thing, that you should own it. For the hackers out there, feel free to checkout my Drywall project, which is a website user system build for node. https://news.ycombinator.com/item?id=4951605