21–30 of 88 posts
> UnQLite is 100% hand-coded, written in ANSI C, Thread-safe, _Full reentrant_ ...
It also uses its own scripting language
> [jx9] uses a clean and familiar syntax similar to C, JavaScript and JSON
The copy on this site leaves me puzzled.
I understand that NoSQL literally means "no SQL," but typically it's a buzzword reserved for unconventional datastores used under heavy distribution.
Maybe you'd want a local embedded "NoSQL" to act as a local datacache? But then for that use case why create an impedance mismatch with the central datastore by rolling your own?
Jx9? So wait, I need another language to interact with the thing that's already embedded directly within my program?
Local offline data analysis? Now that makes sense. Does this have intelligent/optimized paging mechanisms? I have a feeling not, since the author seems to be couching this as an alternative to sqlite for people who like NoSQL.
I'd sincerely love to hear more about what's motivating this project. Was it just for yucks, or is there some problem that the author(s) needed to solve that wasn't well-solved by another tool?
Why use something new with no apparent benefits? (and a lot of drawbacks)
http://en.wikipedia.org/wiki/Berkeley_DB
http://en.wikipedia.org/wiki/Kyoto_Cabinet
Edit: For extra points, read this: http://www.aosabook.org/en/bdb.html
As a hacker/tinkerer type programmer I can understand why it might be fun to build something like this. All of the data structure fun with none of the distributed difficulty! NoSQL! I can even build in that cool new language I've been designing in my head! But like everyone else I'm straining to see a use case. "Serverless" NoSQL? If you've got something small enough that you want an embedded datastore, why use a NoS…
As a hacker/tinkerer type programmer I can understand why it might be fun to build something like this. All of the data structure fun with none of the distributed difficulty! NoSQL! I can even build in that cool new language I've been designing in my head! But like everyone else I'm straining to see a use case. "Serverless" NoSQL? If you've got something small enough that you want an embedded datastore, why use a NoS…
The problem isn't the author's lust for tinkering and improving his dev chops. The problem is with HN, how it's designed to drive fads and constantly disturb our focus, and immature developers who change tech stacks as if it was underwear.
Whether or not it's useful to myself or this community, it's something which someone very intelligent spent a significant amount of time to build. I'd argue that its usefulness is unrelated to how interesting it is. It genuinely makes me want to know more about the author(s) and what their motivation was.
Not that I am envious for the karma, but I wonder why this was not merged into my exactly identical submission 1 hour earlier ( https://news.ycombinator.com/item?id=5749969 ) -- afaict there was no ?repost or similar stunt ...
Nice, I'm currently using SQLite for key value storage, because there aren't better light options afaik. Python shelve module is totally useless with multi gigabyte tables and millions of keys.