Isn't git most of the time used centralized? And that offers better user experience than doing it some decentralized way? It seems to me like most prefer centralized use of git. Be it private server or some large server.
If we compare the traffic of Github vs Bitcoin, Github is likely doing 1,000+ writes per second and Bitcoin is doing what, 5-7 maybe higher with specialized stuff?
Github is nowhere near the world's "central and only" service for Git, so what am I missing to not laugh about?
The downside of a global distributed database (no matter what) is the speed of light, if you need ordering in any transaction you are in trouble, and no classic service requires that for all transactions in its scope, we figured out partitions, row locks, and shards a long time ago.
That's the thing about blockchain/"distributed". They are such vauge terms they can apply or not apply to anything depending on what point you need to make in your argument.
Git is nice distributed tech. It's permissioned, though. Good old permissioned distributed tech. Which predates Bitcoin (obviously, as git is older than Bitcoin).
Yeah, and I always say git with commit signing is a cryptographic block chain in the loosest sense. But in this context I was of course referring to the proof of work/stake BS. In git the proof of work is the work you put into writing the source code. There is actual value in it, not just fictional speculative value.
Git manages pretty much everything by using the `.git` folder created by `git init` and there is (as far as I am aware) nothing stopping you from going into that .git folder and running init again there to start using git to manage the internal state of your repository. At least... that is what I assumed the joke was.
Well, it is all local until you push so you can do whatever you want.
With that said, it obviously is not meaningless at a technical level because without the commit there is nothing to push or merge. On top of that, at a non-technical level it can be extremely helpful to record some plain-english prose to describe why you are changing something. If you find yourself doing that too often you need to narrow your definition of what constitutes a "change" and/or be more discerning about what you work on simultaneously.
Out of curiosity, if you do not use git, what do you use for version control and change-management?
> I have some sort of medium, copper, fiber whatever and I would like to send 10 bytes to the other side of it. What is the right foundations that would lead to an implementation which isn't overly complex.
The bane of every project is understanding what you actually need to do
For example, it is entirely possible that the "right foundation" for your proposed scenario is: Hook one end up to a lightswitch, the other to a light bulb, hire two operators trained in morse code. Then once the 10 bytes are sent write them their cheques and shut it down.
reply