this post was submitted on 14 Aug 2024
88 points (95.8% liked)
Programming
17528 readers
219 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
But Git is so great because it is so decentralised. Everyone says that. I should use Git, they say, because Git still works offline and it's so decentralised. And doesn't depend on centralised servers like ‘the evil SVN’. Then that shouldn't be a problem for anyone ;-)
Git and GitHub are not the same thing
I know. and there are many other ways to host your code. The current GitHub outage shows that most Git users just can't live without a commercial entity stewarding their code though.
It's a convenient way to work together remotely. I'm in the US and my partner for a project is in Portugal. GitHub isn't the only solution, but it's very convenient.
Yeah, saying “most GitHub users can’t live without a commercial entity” is such a nonsense. GitHub is successful while it works well. The moment it doesn’t, there will be other services.
I don't see it. How does downtime show that?
The reactions are shocked enough.
Git being useful decentralized doesn't conflict with the fact that a centralized remote is convenient.
A ton of people using github barely understand the different between github and git and often think they are the same thing or that github and git are somewhat related more than they really are.
Git repos are still decentralized. It's just Github was failing, the thing centralized and synced to. The point of Git being decentralized is, being able to take any of the Git repo copies of the current working developer, and host it on a Github alternative. Meaning the code and project did not get lost because of Github. It's not that such an outage wouldn't be a problem, it's just such an outage is still a problem that can be solved and not a showstopper in the longrun.
Even if Github suddenly cease to exist, out of nowhere, everyone who has a repo copy can setup such a server and work on it as nothing was happened (minus the Github features and hopefully nobody uses the Github app). I believe this is not the case with SVN. If the main repo gets corrupted or destroyed, then its an unsolvable problem. Unless you have a backup. And on Git everyone working on the project has basically a backup.
In short, Git itself works offline. But if you are dependent on Github and its features and applications, then it becomes a problem. So I don't know why SVN is mentioned as the savior here.
SVN has become notably better over the past few years, but let me clarify that my comment was not meant as a reason to use SVN.
Yes. The fact that git is decentralised means you can still carry on working and making commits while GitHub is down. With SVN your basically have to down tools.
What is your point? All the things you say are true but the tone seems to indicate sarcasm?
Public facing projects are 90% Github.
That isn't the fault of git but of people who still haven't learned that you don't put all your important eggs in one basket.
SVN is trash and the people who advocate for it over git are probably pretty crappy developers.
Reason being, if they have trouble understanding git, I have little faith in their ability to create competent code.
How is SVN “trash”?
Then set up your own server.
Like https://git.30p87.de
I realise that this is theoretically possible. But I don't have a problem that I need to solve right now. Others, on the other hand, seem only too happy to make themselves dependent on monopolistic corporations.
the biggest problem isn't that people use github for code hosting; it's that they also rely on github for hosting releases.
True.
I mean.. yes those are true? lol.
I can see that.
You can still push your changes to a different remote on a different service.
Amazing how many replies to your comment completely miss the point
Not surprising me.
Maybe they should have actually made a point then