this post was submitted on 07 Jul 2024
483 points (92.4% liked)

Memes

45130 readers
1336 users here now

Rules:

  1. Be civil and nice.
  2. 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] Tja@programming.dev 2 points 2 months ago (1 children)

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

[–] _MusicJunkie@beehaw.org -2 points 2 months ago (4 children)

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

[–] Asyx@lemmy.ml 9 points 2 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.

[–] perishthethought@lemm.ee 5 points 2 months ago* (last edited 2 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.

[–] Thann@lemmy.ml 2 points 2 months ago

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

[–] Thann@lemmy.ml 3 points 2 months ago (1 children)

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

[–] _MusicJunkie@beehaw.org 0 points 2 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.

[–] Thann@lemmy.ml 3 points 2 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

[–] Tja@programming.dev 3 points 2 months ago

Otherwise you get git. You're describing svn.