GitHub Will Prioritize Migrating To Azure Over Feature Development (thenewstack.io)
- Reference: 0179777042
- News link: https://developers.slashdot.org/story/25/10/14/0833202/github-will-prioritize-migrating-to-azure-over-feature-development
- Source link: https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/
> After acquiring GitHub in 2018, Microsoft mostly let the developer platform run autonomously. But in recent months, [1]that's changed . With GitHub CEO Thomas Dohmke leaving the company this August, and GitHub being folded more deeply into Microsoft's organizational structure, GitHub lost that independence. Now, according to internal GitHub documents The New Stack has seen, the next step of this deeper integration into the Microsoft structure is moving all of GitHub's infrastructure to Azure, even at the cost of delaying work on new features.
>
> [...] While GitHub had previously started work on migrating parts of its service to Azure, our understanding is that these migrations have been halting and sometimes failed. There are some projects, like its data residency initiative (internally referred to as Project Proxima) that will allow GitHub's enterprise users to store all of their code in Europe, that already solely use Azure's local cloud regions.
[1] https://thenewstack.io/github-will-prioritize-migrating-to-azure-over-feature-development/
So it gets hacked at well? (Score:2)
I mean MS cannot get Azure authentication and authorization right. They have demonstrated that now multiple times.
good news, bad news (Score:2)
Good news: no new misfeatures for a while
Bad news: migrating to Azure will probably break everything occasionally.
Familiar... (Score:2)
It was widely rumored that in 1998 Microsoft tried to force Hotmail to use Microsoft infrastructure and met with predictably miserable results. Hotmail was more about trying to show off their infrastructure products that as an offering in and of itself.
Microsoft might be a bit more conflicted on github, but clearly that sentiment persists.
My Codeberg account is all setup and ready to use (Score:2)
I've been hosting my open-source projects on Github for years.
Why you ask? After all, isn't every open-source and free software advocate's duty to stay clear away from Microsoft?
Here's my reason: I only use the git part of Github. I don't use any of Microsoft's proprietary crap on top of it.
Therefore, Microsoft has no vendor lock-in on me: my projects are one git-push away from being hosted elsewhere. I waste their resources by making them host my massive files for free and they have absolutely nothing to s
Re: (Score:2)
+1 for Codeberg. Codeberg is good, and Forgejo (the FOSS code behind Codeberg) is an absolute pleasure to self host, for anyone comfortable with self hosting.
For those considering alternatives, be aware that Gitlab is very "Push AI at you" at the moment. It was a high quality product, and if AI is your thing it's probably fine, but even the self hosted community edition version creates undeletable "AI users" despite supposedly not using it - which makes me suspicious they're going to go all-in on AI enshitt
Re: (Score:2)
May still get hacked when MS has the next Azure security disaster ...
Next up: Mandatory M$ account! (Score:2)
Even under threat of EU, M$ did not properly offer Consumer ESU for win10, instead they secretly patched out the ability to use a local-account and now force EVERYONE into an M$ account. (And until yesterday, win10 would display that activating ESU is not ready yet in the region.)
The same will happen to GitHub, like you are forced into that forsaken account for Minecraft, GitHub will transition all accounts into M$ accountsâ¦
M$ has been trying hard to appear cool lately, but the ugly truth of M$ o
In other news, companies have priorities (Score:2)
Often, doing one thing means not doing something else. With MS owning github, I'm sure whatever they're using for hosting now has become a harder conversation when the parent company has their own infrastructure for that. In my career, I've done a couple of infrastructure moves (colo to different colo, colo to cloud) and it's surprising how much can be involved.
Let the Enshittification commence (Score:1)
Local server here we come.
Microsoft GitHub Azure .. (Score:2)
Microsoft June 2018: "GitHub will retain its developer-first ethos and will operate independently to provide an open platform for all developers in all industries"
Re:GitHub - Azure (Score:2)
Well, if it ain't broken, don't fix it. Microsoft might have broken it some since the acquisition but I'd expect more in the move to Azure.
From the article:
> GitHub has recently seen more outages
I would expect more during and maybe even after the move.
Anyway, we don't rely on github for our own stuff. It might be a bad idea to put your industrial secrets on a publicly hosted cloud IMHO. We run our own instance of gitlab in house but you could get by with more light weight solutions.
Let's hope the move goes smoothly for those relying on github! I
Re: (Score:2)
Might also get hacked with the rest of Azure now. MS cannot get Azure security right.