Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by blibble | Hacker News Reader

Parent Full thread

blibble·

I wouldn't be surprised if there isn't some plan to make all of GitHub's backend "legacy"

and switch everyone to the dumpster fire that is Azure DevOps

and if you thought GitHub Actions was bad...

View on HN

When Microsoft bought GitHub they cancelled GitHubs own early CI effort and rebranded the existing Azure DevOps as GitHub Actions.

The GitHub Actions runner source code is all dotnet. GitHub was a Ruby shop.

I believe the original GitHub Actions was in Go - it used HCL which was at that point only really implemented in Go. Quite the move backwards to switch to YAML.

IIRC Azure DevOps was the “dead one”, all new development only takes place on GitHub.

From my perspective, Azure Pipelines is largely the same as GitHub Actions. I abhor this concept of having abstract and opaque “tasks”.

There's direct evidence that GitHub Actions was the rewrite of Azure Pipelines that was originally planned to finish 5 years ago and got "stuck" (because all their resources moved to GitHub). For a while you could find 2020 roadmap repositories (on GitHub) for AzDO talking up a Pipelines rewrite bringing a lot more features (including better Docker alignment versus Pipelines' much more complex "runner skills") that instead showed up in the first version of GitHub Actions.

Microsoft claims Azure DevOps still has a roadmap, but it's hard to imagine that the real roadmap isn't simply "Wait for more VPs in North Carolina to retire before finally killing the brand".

> I wouldn't be surprised if there isn't some plan to make all of GitHub's backend "legacy"

> and switch everyone to the dumpster fire that is Azure DevOps

The other way around. Azure DevOps is 1/2 a backend for Github these days. Github re-uses a lot of Azure Devops' infrastructure.

Reply on news.ycombinator.com