5 ms·

Indeed. The fact that nobody seems concerned about Github/Microsoft monopoly is concerning to say the least. https://ploum.net/2023-02-22-leaving-github.html h

by ploum 3y ago

Indeed. The fact that nobody seems concerned about Github/Microsoft monopoly is concerning to say the least. https://ploum.net/2023-02-22-leaving-github.html https://ploum.net/2023-02-22-leaving-github.html

dcgudeman 3y ago
Really confused why people don't seem to use the term "monopoly" correctly. Monopoly: the exclusive possession or control of the supply of or trade in a commodity or service. Github does not have in any sense exclusive possession or control of hosted version control. It is a popular choice, that's it.
- kstrauser 3y ago
  I agree. GitHub is the biggest player, but it's a pretty layer on top of an inherently distributed system. If I get tired of Microsoft's shenanigans, I can pack up move to a competitor with only the normal amount of friction (like moving bug reports over, etc.). I use Gitea for my personal projects and it handles 95% of the code-hosting bits just as well.
  - mjw1007 3y ago
    I'm not so relaxed about how easy it will be to move to a new issue tracker. When you're moving from a self-hosted system to a proprietary system, you can do the work yourself to make sure there are redirects from the old URLs to the new ones. That option isn't likely to be available when you're moving the other way. I observe that github is happy for you to "bring your own domain" for github pages, but AIUI issue and PR URLs are always under github.com .
    - kstrauser 3y ago
      Maintaining links is going to be a pain in the neck, sure. I don't mean to make light of it. However, that's kind of inherent with going from one service to another, and not something GitHub's doing to make it artificially harder.
mjw1007 3y ago
I agree. I'm not, at this stage, tremendously worried about Microsoft finding ways to use its control of Github to get its own way in some kind of conflict. I am worried about what happens if, or when, Github's owners decide it's time to stop caring about having a good reputation and instead squeeze it for as much profit as possible (what we seem to be calling "enshittification" these days). Pointing git remotes somewhere different shouldn't be a huge pain, but all those issue trackers are a different matter.

by ploum 3y ago

dcgudeman 3y ago

Really confused why people don't seem to use the term "monopoly" correctly. Monopoly: the exclusive possession or control of the supply of or trade in a commodity or service. Github does not have in any sense exclusive possession or control of hosted version control. It is a popular choice, that's it.

kstrauser 3y ago
I agree. GitHub is the biggest player, but it's a pretty layer on top of an inherently distributed system. If I get tired of Microsoft's shenanigans, I can pack up move to a competitor with only the normal amount of friction (like moving bug reports over, etc.). I use Gitea for my personal projects and it handles 95% of the code-hosting bits just as well.
- mjw1007 3y ago
  I'm not so relaxed about how easy it will be to move to a new issue tracker. When you're moving from a self-hosted system to a proprietary system, you can do the work yourself to make sure there are redirects from the old URLs to the new ones. That option isn't likely to be available when you're moving the other way. I observe that github is happy for you to "bring your own domain" for github pages, but AIUI issue and PR URLs are always under github.com .
  - kstrauser 3y ago
    Maintaining links is going to be a pain in the neck, sure. I don't mean to make light of it. However, that's kind of inherent with going from one service to another, and not something GitHub's doing to make it artificially harder.

mjw1007 3y ago

I agree. I'm not, at this stage, tremendously worried about Microsoft finding ways to use its control of Github to get its own way in some kind of conflict. I am worried about what happens if, or when, Github's owners decide it's time to stop caring about having a good reputation and instead squeeze it for as much profit as possible (what we seem to be calling "enshittification" these days). Pointing git remotes somewhere different shouldn't be a huge pain, but all those issue trackers are a different matter.