Cloud
Post #7313 · source on Telegram
GitHub Prioritizes Azure Migration Over Feature Development: Reddit Reacts
Description
A screenshot of a Reddit post on r/programming titled 'GitHub Will Prioritize Migrating to Azure Over Feature Development' with a link to thenewstack.io. The post features a cute Octocat (GitHub mascot) figurine in front of a computer screen. It has 120 upvotes and 50 comments. The top comment by user roscoelee (310 upvotes, 1h ago) reads 'It's nice to know that migrating to azure is difficult for a Microsoft acquisition too.' The humor is in the irony that even Microsoft's own subsidiary struggles with Azure migration, validating every developer's experience that cloud migrations are painful regardless of corporate backing
More like this
More like this in Cloud →
Use J and K for navigation
Comments
20Comment deleted
When even Microsoft can't make Azure migration easy for their own acquisition, you know your team's '6-month migration estimate' is actually measured in geological epochs
The GitHub-to-Azure migration is the enterprise version of refactoring a legacy system: the budget is infinite, the timeline is 'when it's done,' and the only user-facing feature is a longer list of known issues
Apparently the new roadmap is `git remote add origin azure && git push --force`, because nothing says enterprise synergy like blocking pull requests until the cloud bill is under the same parent company
Even Microsoft's own acquisitions need a three-year roadmap, two architecture reviews, and a sacrificial goat to successfully migrate to Azure - turns out 'lift and shift' is more like 'lift, shift, pray, and hire consultants'
When your new parent company's cloud migration becomes more important than shipping features, you know the honeymoon phase is over. Even Microsoft finds migrating to Microsoft hard
Acquisition math: convert epics to landing zones, implement in Bicep, and call the vendor lock‑in “modernization.”
Post-acquisition glow-up: features forked to 'later', Azure migration merged to master
Say no to "the cloud" - put your servers in your own basement, use excess heat as a heat source during winter :) Comment deleted
i have my little server in my room and pc which i got free heat and in summer i put them outside Comment deleted
And you can watercool them with standard house radiators so pumps would be the only noise generators. Comment deleted
For now, my shittiest expirience ever is with Apple Podcasts Connect API doc: it's hidden behind login (you can get credentials only directly from Apple), it has close to nothing explained and it has links to types that don't lead anywhere. I'm struggling to do the simplest things🙄 Comment deleted
I see people reverse engineering to get the api endpoint for azure to workaround some automation😂 Comment deleted
There's four az APIs IIRC, and resource naming is quite so inconsistent which makes it hell for devops Comment deleted
Azure's AI api (all services are a mess) Comment deleted
AI api was especially cursed as to me taste Comment deleted
Eg it would give non-working code examples with deprecated API versions after model "deploy" 🌚 Comment deleted
I still remember when microsoft was set to buy github. Most sane people noped tf out of it to gitlab and other alternatives. They will keep on taking corporate driven retarded decisions like they did for xbox and their many studios. Never go mainstream lads Comment deleted
Github only sold because it wasn't profitable Comment deleted
GitLab is completely different from GitHub Comment deleted
They want users to use copilot trained on documentation to get money from them. Comment deleted