Okay, I get it, but they also abandoned maintaining their Terraform provider! What a joke! They don't even want to open its maintenance and development to the community! How can you manage hundreds and thousands of repos manually?! It's always been a terrible provider - slow, buggy, and severely behind the latest GitHub features, but now it's literally dead! They openly claimed to be focusing their energy on API development, and until the API is fixed, they will continue working on the provider. This is unacceptable!
GitHub will prioritize migrating to Azure over feature development
61–67 of 67 posts
Re: GitHub will prioritize migrating to Azure over feature development
#62Earlier quoted context omitted.
meanwhile openai is concentrating on making spongebob squarepants police chase videos
How much do you think that meaningfully distracted them from general capabilities-acceleration work? I think not very much, so this doesn't seem like much of an argument.
if you convincingly thought you were in a race to AGI you'd be spending every single resource on it to try and beat the competition
not burning human effort and quintillions of CPU cycles on mickey mouse videos (literally)
Re: GitHub will prioritize migrating to Azure over feature development
#63I've never done a migration at a scale like this, but I have seen infra at similar scale, and I can't imagine how difficult this will be in a 12 month period. How big are github's ops/dev teams? That seems like a really unrealistic target to me. I expect outages.
In practice, I'd expect the majority of servers to go through a tool based lift and shift like Azure Migrate. That's what we're using to migrate around 6k state government servers to the cloud. Where there are opportunities for low hanging modernization, we'll take that route. Like migrating to SQL Managed Instances rather than pushing to SQL in a VM.
Re: GitHub will prioritize migrating to Azure over feature development
#64This is good news right? People complain about them having bloated it with too many features. If this keeps them from making it even more of an ridiculous AI editor rather than something that complements an editor, that would be great.
Absolutely! I've been complaining about this exact problem for a while: stop pushing AI features no one asked for and improve the reliability.
I just hoped they would fix the mess that are GitHub notifications: https://github.com/orgs/community/discussions/15747
Re: GitHub will prioritize migrating to Azure over feature development
#65I hope they are prepared for lots of headaches, random outages, slow (did I say S-L-O-W) tooling and infrastructure, terrible access to GPU's, at least 2-3x more expensive than any other cloud. Support is staffed by overseas Indians who drag every interaction out and just wear you down until you give up.
> Support is staffed by overseas Indians who drag every interaction out and just wear you down until you give up You really think they, not unlike most top of the crop MSFT partners, get support out of India? Try directly from the teams in Redmond.
Are you joking? You obviously never worked with Microsoft, or been a part of any of their deals. OpenAI absolutely will not get anything special. In fact, because of all the attention, they will probably even get worse service than a regular user. It makes no sense, but that's how they operate.
Re: GitHub will prioritize migrating to Azure over feature development
#66I hope that Microsoft will not smash GitHub UX to something like Azure Devops. UX of Azure services is terrible, even compared to AWS.
Re: GitHub will prioritize migrating to Azure over feature development
#67Obviously this makes sense from a dog-fooding perspective because the cloud provider (Microsoft) owns the product (Github), but I'm always surprised when very capable tech companies decide they aren't capable of running bare metal. Running your own servers was never rocket science, it was literally the only option 20 years ago. Every startup used to have a rack of servers in a closet. I have always thought of cloud h…
I agree with this. It makes total sense for startup, but not for large profitable company, full of smart people. Look at Basecamp cloud exit, good example.