Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub will prioritize migrating to Azure over feature development

thenewstack.io

Post reply on HN
Print view View original

41–50 of 67 posts

Re: GitHub will prioritize migrating to Azure over feature development

#41

Post by blibble »

ameliaquining wrote: post #27
827a wrote: post #6

> The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months. I find it interesting to compare timelines like this (which is very reasonable and expected for an organization of Github's size) with, for example, how AI 2027 describes the world will look like in October 2027. In the next 24 months, if all these timeslines are to be believed, AI will have cured cancer, agent-5 will be…

This discrepancy is precisely the reason (or at least one reason) why AI 2027 hypothesizes that all the interesting developments will be happening inside whichever AI lab is in the lead. The kind of AI agent that AI 2027 hypothesizes in that timeframe could do the migration in much less than 24 months, but only if the organization completely changes how it works internally so that everything is driven by the goal of…

meanwhile openai is concentrating on making spongebob squarepants police chase videos

Re: GitHub will prioritize migrating to Azure over feature development

#42

Post by walkabout »

stackskipton wrote: post #14
walkabout wrote: post #10

Earlier quoted context omitted.

The infrastructure behind serving git repos the way they do is pretty fiddly—I'd not be a bit surprised if this move reduces stability and/or performance.

Sure but it also might make them fix some of that.

No, I mean inherently so. It's basically a whole stack of caching problems.

Re: GitHub will prioritize migrating to Azure over feature development

#43

Post by mhitza »

avtar wrote: post #39
nitwit005 wrote: post #36

I essentially don't want any more GitHub features, so this sounds totally positive.

It would be great if Actions received some polish. How are people applying org/team wide policies such as job timeouts to avoid burning through monthly limits? Last I checked this wasn’t a feature :/

You can draft up your own json schema and apply it as a validation check when PRs are created. Or just use a proper programming language for the yaml checks.

You can pair that up with a template repository for the org and everyone can start new projects from that template (which contains the workflow to check future workflow files).

If you want assistance with organisation-wide code policies, I can help and my email is in my profile.

Re: GitHub will prioritize migrating to Azure over feature development

#46

Post by phatfish »

827a wrote: post #6

> The plan, he writes, is for GitHub to completely move out of its own data centers in 24 months. I find it interesting to compare timelines like this (which is very reasonable and expected for an organization of Github's size) with, for example, how AI 2027 describes the world will look like in October 2027. In the next 24 months, if all these timeslines are to be believed, AI will have cured cancer, agent-5 will be…

Wow, that AI 2027 thing is some real dedicated OpenAI fan fiction.

Re: GitHub will prioritize migrating to Azure over feature development

#47

Post by phatfish »

sam_lowry_ wrote: post #32
jasonthorsness wrote: post #15

It makes sense given "CTO Vladimir Fedorov notes that GitHub is constrained on capacity in its Virginia data center." and Azure has a decent setup for their AI support infrastructure and base virtual machines. But having gone through a data center migration; depending on how "unique" some of their existing setup was; I do not envy them in this process (and I estimate this will take double the expected time :P).

Vladimir Fedorov just joined Github from Meta a few months ago. What does he know?

At the very least it seems like someone had told him "we are constrained on capacity in our Virginia data center".

Re: GitHub will prioritize migrating to Azure over feature development

#48

Post by iamleppert »

I 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.

Re: GitHub will prioritize migrating to Azure over feature development

#49

Post by transcriptase »

blibble wrote: post #41
ameliaquining wrote: post #27

Earlier quoted context omitted.

This discrepancy is precisely the reason (or at least one reason) why AI 2027 hypothesizes that all the interesting developments will be happening inside whichever AI lab is in the lead. The kind of AI agent that AI 2027 hypothesizes in that timeframe could do the migration in much less than 24 months, but only if the organization completely changes how it works internally so that everything is driven by the goal of…

meanwhile openai is concentrating on making spongebob squarepants police chase videos

That’s not fair.

I also saw a creepy cat in the hat breaking into someone’s home and take a shotgun round to the chest.

Re: GitHub will prioritize migrating to Azure over feature development

#50

Post by dnadler »

ryandvm wrote: post #35

Obviously 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…

It’s not that they don’t have it. It’s that they don’t want it.
Post reply on HN