3 ms·
Definitely path of least resistance but also bound to get us a monoculture
by Havoc 3y ago
Definitely path of least resistance but also bound to get us a monoculture
- Tuna-Fish 3y agoThe monoculture already exists, and it was always going to be formed. The one good thing is that git makes it relatively easy to move, so that if Github suffers excessive enshittification, something else can steal their lunch.
- kibwen 3y agoGit makes it relatively easy to move the code itself and its commit history, but not the other things people use Github for: issues, automation, CI... The lock-in is there.
- zelphirkalt 3y agoMaybe this is making a good argument for managing these things as commits in a directory in the git tree?
- jbaber 3y agoThere are a few attempts to do this (git-bug is the most recent I remember). I desperately want one to get traction. git-bug even has a way to bridge your issues to github/gitlab/etc. trackers.
- LightFog 3y agoMSFT gobbling up your code and selling it back to you isn’t enshittified enough for you?
- mathstuf 3y agoYou can move the code, sure. It's the infrastructure that is hard to relocate (issues, pulls). If one uses references like `#123` in the history, you need to do something to keep them "alive" on a migration. GitLab itself has an interesting solution where instead of short references, full URLs are used so that they work in any context (including locally). These URLs are then rendered as `#123` or whatever depending on the location of the render.
- fsckboy 3y ago>git makes it relatively easy to move, so that if Github suffers excessive enshittification... what if the enshittification is making it hard to move?
- mbreese 3y agoThe network effects associated with hosting code in a public source repository are just too great. If you want your code to be seen, used, trusted, you put it on one of the primary code repositories. At one point, this was sourceforge. For a while bitbucket had a good share. Then came GitHub. There are also always a few secondary repositories that share the same tooling, but still have less traction (like GitLab). But the network effects of GitHub are hard to ignore. But, like was said in a previous comment, it least it is easy to move Git repositories from one host to another. So when there is an inevitable successor to GitHub, we’ll all be able to migrate to the next hotness easier. (That’s assuming that the next hotness supports Git. Prior shifts followed from changing underlying technologies… CVS -> SVN or Hg -> Git)
- cybrox 3y agoEven ignoring the userbase, GitLab or BitBucket would have a better chance at hosting thriving projects. Sourcehut has a very good and noble idea but it just adds so much complexity in the name of purity to a hurdle that is already very big for newcomers. They basically undo all the progress on collaboration since the 90s to get rid of the modern problems that these changes cause, without realizing that the way forward is to solve these problems, not just revert to a time when they didn't exist.
- Pet_Ant 3y ago> They basically undo all the progress on collaboration since the 90s to get rid of the modern problems that these changes cause, https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_fence https://en.wikipedia.org/wiki/G._K._Chesterton#Chesterton's_...
- aidenn0 3y ago> They basically undo all the progress on collaboration since the 90s to get rid of the modern problems that these changes cause, without realizing that the way forward is to solve these problems, not just revert to a time when they didn't exist. Saying they are "reverting to a time when they didn't exist" is missing the point. It's about improving the problems that caused people to switch away from the collaboration tools in the 90s; e.g. [1]. So it's more of a fork of the 90s than a rollback. Also, it's not like the people at SH (and their users) haven't tried new collaboration tools. I (at least) have tried them and found them wanting in important ways. The conclusion that it's better to fix the older tools than the newer tools could be debated with[2], but nobody's sticking their heads in the sand here. 1: https://sourcehut.org/blog/2022-07-06-sourcehut-and-irc/ https://sourcehut.org/blog/2022-07-06-sourcehut-and-irc/ Note also that even without SH, e-mail, IRC, &c. are all greatly improved in both small and large ways in the time between the 90s and now. 2: I mean everybody involved with SH already prefers the older tools for one reason or another, so fixing the older tools is going to be the obvious path forward for them.
- busterarm 3y agoIt's not about purity. It's about a workflow where everything lives in email rather than some company's walled garden. It also doesn't give a toss about newcomers. It's for users who want something very specific and know what that looks like already. It's like the same reasons that OpenBSD still uses CVS -- it works perfectly fine for those involved in the project and the switch to Git would not only take time away from what's important to work on but also add a ton of noise from new contributors who may not have the same goals as the project.