Yup.
I was at GitHub Universe last week. It's very clear GitHub (Microsoft) is trying to become like AWS but for the SDLC instead of for runtime.
Soon we'll all be using GitHub full-time to do all our coding in the browser with integrated runtime envs and CI and AI along for the ride. You get a taste with some fancy OSS demo projects which they do legitimately support. Then you want to integrate with those OSS libraries, so you have to dip your toes into GitHub's ecosystem. And if you want updates and security and to not have public repos ... then time to pony up.
GitHub does support OSS in real ways, but it's pretty obviously a loss-leading marketing / freemium strategy. It's not surprising they give themslves a pat on the back - it's marketing after all. This is not a bad or even amoral thing, but let's not be naive.
They're eating their competitors' lunch. Many of the vendors at GitHub Universe had feature-sets that had clear overlap with GitHub's own ambitions, particularly in the security space. GitHub can and will put them out of business when the opportunity strikes. These ambitions are clear. C'est la vie.
What's less clear is how developer-friendly the ecosystem will remain when everything is locked into GitHub's world,. And it's even less clear how they will ratchet up pricing (or ratchet down interoperability or industry standards) as more gets sucked in.
It is an enterprise B2B company and a part of Microsoft, for better and for worse.
In most other cases of technology choices, work and personal environments can differ a lot (languages, operating system, development machine, database systems, …). That makes choices less sticky.
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.
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 .
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.
I do not know of any other platform that gives you completely free CI/CD, there is either a usual limit or its a paid feature.
Microsoft, for whatever reason, is betting on Python.
I wonder whether Github would have considered the PSF to be "wonderfully welcoming" if they hadn't switched from their self-hosted bug tracker to Github's offering last year.
Personally I don't find being asked to read [1] before I can submit a bug report at all welcoming.
[1] https://docs.github.com/en/site-policy/github-terms/github-t...