Fragile narrow laggy asynchronous mismatched pipes kill productivity
I think git is a good model for what would otherwise be "laggy async and mismatched" distributed systems.It has a fast sync algorithm, and after you sync, everything works locally on a fast file system.  You explicitly know when you're hitting the network, rather than hitting it ALL THE TIME.-----I would like to use something like git to store the source code to every piece of software I use, and the binaries.  That is, most of a whole Linux distro.I have been loosely following some "git for binary data" projects for a number of years.  I looked at IPFS like 5 years ago but it seems to have gone off the rails.  The dat project seems to have morphed into something else?Are there any new storage projects in that vein?  I think the OP is identifying a real problem -- distributed systems are unreliable, and you can get a lot done on a single machine.  But we are missing some primitives that would enable that.  Every application is littered with buggy and difficut network logic, rather than having a single tool like git (or rsync) which would handle the problem in a focused and fast way.It would be like if Vim/Emacs and GCC/Clang all were "network-enabled"... that doesn't really make sense.  Instead they all use the file system, and the file system can be sync'd as an orthogonal issue.Sort of related is a fast distro here I'm looking at: https://michael.stapelberg.ch/posts/2019-08-17-introducing-d...