Fragile narrow laggy asynchronous mismatched pipes kill productivity
I think git is a good model for what would otherwise be &quot;laggy async and mismatched&quot; distributed systems.<p>It has a fast sync algorithm, and after you sync, everything works locally on a fast file system.  You explicitly know when you&#x27;re hitting the network, rather than hitting it ALL THE TIME.<p>-----<p>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.<p>I have been loosely following some &quot;git for binary data&quot; 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?<p>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.<p>It would be like if Vim&#x2F;Emacs and GCC&#x2F;Clang all were &quot;network-enabled&quot;... that doesn&#x27;t really make sense.  Instead they all use the file system, and the file system can be sync&#x27;d as an orthogonal issue.<p>Sort of related is a fast distro here I&#x27;m looking at: <a href="https:&#x2F;&#x2F;michael.stapelberg.ch&#x2F;posts&#x2F;2019-08-17-introducing-distri&#x2F;" rel="nofollow">https:&#x2F;&#x2F;michael.stapelberg.ch&#x2F;posts&#x2F;2019-08-17-introducing-d...</a>