Let’s make a thought experiment. Suppose that I have a data format and a store that resolves the issues in the post. It is like git meets JSON meets key-value. https://github.com/gritzko/go-rdx

What is the probability of it being used? About 0%, right? Because git is proven and GitHub is free. Engineering aspects are less important.

▲

pdimitar 2 hours ago | parent | next [-]

I am very interested by something like this but your README is not making it easy to like. Demonstrating with 2-3 sample apps using RDX might have gone a long way.

So how do I start using it if I, for example, want to use it like a decentralized `syncthing`? Can I? If not, what can I use it for?

I am not a mathematician. Most people landing on your repo are not mathematicians either.

We the techies _hate_ marketing with a passion but I as another programmer find myself intrigued by your idea... with zero idea how to even use it and apply it.

▲

stkdump 8 hours ago | parent | prev [-]

Sorry, I am turned off by the CRDT in there. It immediately smells of overengineering to me. Not that I believe git is a better database. But why not just SQL?

▲

gritzko 8 hours ago | parent [-]

Merges require revisioning. JSON or SQL do not have that in the model. This variant of CRDT is actually quite minimalistic.

▲

stkdump 7 hours ago | parent [-]

I would argue LWW is the opposite of a merge. It is better to immediately know at the time of writing that there is a conflict. CRDTs either solve or (in this case) don't solve a problem that doesn't really exist, especially for package managers.

	▲	gritzko 7 hours ago \| parent [-]
		Git solves that problem and it definitely exists. Speaking of package managers, it really depends. Like, can we use one SQLite file for that? So easy, why no one is doing that?