Smooth Operator

Probably not terribly useful long-term, but for rough purposes you might try https://github.com/disruptek/frosty. It’s kinda designed for “I know what I’m doing” hacks and it could help your differential diagnosis....

It sounds like you're fine with git hashes or versions, as long as the software is usable. Is that right?

I think everyone understands your frustration, and to a large extent, we all share your concerns both with Nim and other language ecosystems, but the point I'm trying to make...

> In theory, if functionality must change to fix a bug that is a bump in the minor version since promised > functionality changed. Hey man, out here in the...

If you want to talk about your technical challenges (_which are mine, as I depend upon your software!_) and how we might work together to solve them, well, you can...

> Sorry, I think I beat you here, https://github.com/Araq/nawabs ;-) I like it, I use it, I recommend it, and I think it's part of the solution, but the fact...

> What did they get wrong? What package management generally gets wrong, in my opinion, is that it makes developers opt-in to most of the workflow that best promotes quality,...

Having versioning semantics that are not shared by all packages will add an expensive burden to all tooling despite the requirement of such semantics existing for perhaps only a small...

Here's a simple nimterop wrapper for lmdb. It's pretty great. Golden isn't a super example of its use, honestly. Maybe I'll finish it someday. - http://www.lmdb.tech/doc/index.html - https://github.com/disruptek/golden Anyway, if...

It sounds like the best course of action is to let @protolambda tell us when the design is fairly stable and then use it to inform the hot/cold storage approach....