OneMeaningManyNames@lemmy.ml to Memes@lemmy.mlEnglish · 4 months agoSo much for Blockchain's real life use caseslemmy.mlimagemessage-square132fedilinkarrow-up1224arrow-down119
arrow-up1205arrow-down1imageSo much for Blockchain's real life use caseslemmy.mlOneMeaningManyNames@lemmy.ml to Memes@lemmy.mlEnglish · 4 months agomessage-square132fedilink
minus-squareTja@programming.devlinkfedilinkarrow-up0·4 months agoCounterpoint: it is a chain and there absolutely is not one server.
minus-square_MusicJunkie@beehaw.orglinkfedilinkarrow-up0arrow-down2·4 months agoFor each project there is one authoritative instance, one “server” that everyone pushes to. Otherwise you get chaos.
minus-squareAsyx@lemmy.mllinkfedilinkarrow-up4·4 months agoThat’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.
minus-squareTja@programming.devlinkfedilinkarrow-up2·4 months agoOtherwise you get git. You’re describing svn.
minus-squareThann@lemmy.mllinkfedilinkEnglisharrow-up2·4 months agoAnd nobody ever forked a project, and lived happily ever after, then end.
minus-square_MusicJunkie@beehaw.orglinkfedilinkarrow-up1arrow-down1·4 months agoIf you want to work with the original project, you have to push to the server that controls the original project.
minus-squareThann@lemmy.mllinkfedilinkEnglisharrow-up3·4 months agoNo you don’t, you can just fork it, add a commit, and walk away, and everyone can decide which one they want to clone
minus-squareperishthethought@lemm.eelinkfedilinkEnglisharrow-up2·edit-24 months agoThat 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.
minus-squareThann@lemmy.mllinkfedilinkEnglisharrow-up1·4 months agoPeople want simple answers, and “blockchain bad” seems to satisfy many
Counterpoint: it is a chain and there absolutely is not one server.
For each project there is one authoritative instance, one “server” that everyone pushes to. Otherwise you get chaos.
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.
Otherwise you get git. You’re describing svn.
And nobody ever forked a project, and lived happily ever after, then end.
If you want to work with the original project, you have to push to the server that controls the original project.
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
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.
People want simple answers, and “blockchain bad” seems to satisfy many