Hacker News Reader

Comment by h3ll0k4ll3 | Hacker News Reader

The design before was targeting developers with a "for work" feel. From a vcs perspective and ci/cd perspective it showed the important stuff. The new file browser is especially bad - being Tritanopia color blind the lack of lines and the folders physically hurt my eyes.

But To be honest we all know what this re-design is for. Microsoft pushing Azure Pipelines ( github actions ). The previous github interface was not cute / nice enough for actions. So they re-designed the entire site to be able to push us towards Azure usage. ( that is the entire reason Microsoft Acquired github - slowly luring developers from opensource to the safe walled garded of microsoft. With a slow shift of Azure cloud offerings leaking in to our minds. ). And slowly taking over most organisations tool-chains.

View on HN

What is an action? And is there really much risk of us using Azure? My code, like most I suspect, runs on linux/unixy things and probably doesn't even build on Windows.

I'm pretty sure I read somewhere that at least 50% of the vms running in Azure are actually running linux.

And in this case, "action" refers to the ci/cd tooling github provides called "github actions". It's one of the tabs at the top.

The risk is determined by us the developers. Actions means "Github Actions - re-branded Microsoft ci/cd tools).

Microsoft uses partners to sell their offerings. Many of these have used cross-selling with the arguments of all eggs in the same basket and buying from one vendor "more secure and safe" for decades. Tools like Github and Some of the best and most creative developers not using Visual Studio threatened this method of selling. (the IDE runs and deploys "solutions" to Azure directly - very effective walled garden ).

The free thinking and creative developers had started to break organisations free from the microsoft "safe basket" and the push towards AWS and GCP was hurtful to the bottom line. To counter this a strategy was formulated.

Microsoft rebranded as the good guys. With an image of participating and actively supporting opensource. First they tried with pushing .NETcore. Then they gave us VS Code. Then they aquired Github. And now the cross-selling is back in the game.

The arguments of "one vendor" and "one basket" is thrown in your face again - when dealing with procurement people and internal organisation politics.

"We argue Microsoft as the better option here - we in procurement have a good relationship with Partner X who have helped us with Office365 for years". "They told us you already have The Github from Microsoft. And our Code already lives in Azure. You in IT really need to motivate why a different vendor is required for all this cloud stuff".

And the herd of sheeps are slowly returning to the garden.

Reply on news.ycombinator.com