Memes

45886 readers

1169 users here now

Rules:

Be civil and nice.
Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago

MODERATORS

[email protected]

497

So much for Blockchain's real life use cases (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

139 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[+] [email protected] -8 points 5 months ago (5 children)

Git is not a blockchain. Most importantly, it's not distributed. There's a singular git server that all git clients for that repository connect to and use as a source of truth.

[–] [email protected] 11 points 5 months ago

Git was built specifically to avoid the necessity to have one authoritative server.

[–] [email protected] 8 points 5 months ago

https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows

In contrast with Centralized Version Control Systems (CVCSs), the distributed nature of Git allows you to be far more flexible in how developers collaborate on projects. In centralized systems, every developer is a node working more or less equally with a central hub. In Git, however, every developer is potentially both a node and a hub; that is, every developer can both contribute code to other repositories and maintain a public repository on which others can base their work and which they can contribute to.

[–] [email protected] 7 points 5 months ago

That is patently false. It was developed to help develop the Linux kernel, which famously has multiple decentralized repositories managed by different maintainers.

The fact that most companies use it in a way you describe, with only one central repository, does not mean that git is not distributed.

[–] [email protected] 6 points 5 months ago* (last edited 5 months ago) (1 children)

I agree it's not a blockchain, (although it has chain properties) but it is kinda decentralized. By convention projects almost exclusively have a single remote, and by convention that single remote is treated as an ultimate source-of-truth... But you can absolutely have the same repo with multiple remotes defined, and one could establish different schemes to determine which branches on which remotes represent what in terms of "truth".

[–] [email protected] 2 points 5 months ago

I've pulled code branches between my computers without publishing to an external server plenty of times. It's a really useful feature to be able to keep stuff in sync with a version history.

[–] [email protected] 2 points 5 months ago (1 children)

Counterpoint: it is a chain and there absolutely is not one server.

[–] [email protected] -2 points 5 months ago (4 children)

For each project there is one authoritative instance, one "server" that everyone pushes to. Otherwise you get chaos.

[–] [email protected] 9 points 5 months ago

That's not a git thing though. You can totally have multiple remotes and the remotes are just git repositories themselves. Git is 100% decentralized. There is technically nothing stopping you from having multiple remotes.

[–] [email protected] 5 points 5 months ago* (last edited 5 months ago) (1 children)

That may be how you use it, but that's not baked into git. See my previous response. There's a bunch of FUD in this thread for some reason.

[–] [email protected] 2 points 5 months ago

People want simple answers, and "blockchain bad" seems to satisfy many

[–] [email protected] 3 points 5 months ago

Otherwise you get git. You're describing svn.

[–] [email protected] 3 points 5 months ago (1 children)

And nobody ever forked a project, and lived happily ever after, then end.

[–] [email protected] 0 points 5 months ago (1 children)

If you want to work with the original project, you have to push to the server that controls the original project.

[–] [email protected] 3 points 5 months ago

No you don't, you can just fork it, add a commit, and walk away, and everyone can decide which one they want to clone