Having worked there around 2020-2021 there were many folks not happy with being forced to use azure and being forced to build GitHub actions based on azure devops. Lots of AWS usage still existed at that time but these days u bet it’s mostly gone.

I would imagine the majority of Github engineers there currently joined post MS acquisition.

That doesn't necessarily mean they're happy about Azure as a backend.

I've been a software "engineer" for over 20 years, and my personal experience is that software engineers are basically never happy.

> personal experience is that software engineers are basically never happy.

Being happy means:

- you don't feel the need to automate more manual tasks (you lack laziness)

- you don't feel the need to make your system faster (you lack impatience)

- you don't feel the need to make your system better (you lack hubris)

So basically, happiness is a Sin.

I’ve used AWS for almost 20 years and I can tell you it’s more stable than Azure

I have zero doubts.

True enough. The world is never as predictable as the computers we program, and the computers we program are never as predictable as we feel they should be.

Plenty of happy engineers at the other cloud. :)

I presume you mean the Oracle cloud?

Nobody is happy with Oracle anything! It has some users because it is free. It has paid users because Larry Ellison bribed the government. Nobody would choose it voluntarily.

No, gcp. Was a happy customer for many years, now I work there.

A bunch less today than a year ago.

Autonomy, decent pay, non toxic environment and non bullshit job.

It isnt actually all that much but most devs who have all of these I've come across are happy.

Agreed. I've had this more often than not, and while every job has its little gripes, if I have those things the rest is well, just part of the job.

> notable that they blame "our upstream provider" when it's quite literally the same company

As in why don't they mention Azure by name?

Or as in there shouldn't be isolated silos?

A few years ago I talked to an developer advocate for Azure. I wanted to know why it took for ever when you wanted a new public IP. My take was that it felt like they went out on the internet to look for an IP to purchase from a 3rd. party. The answer I got was that do to the silos within Microsoft it might as well be a 3rd party supplier. The slowness is exactly because IPs are/were a managed by another Microsoft entity, who views any interaction, even within the company, as hostile.

I get your point, but it just sounds a bit funny when it's an artefact of corporate structure that it's true.

Like imagine if AWS was composed of separate companies for different services - Fargate was an Heroku acquisition say - and then they all went down and blamed their 'upstream provider' because they can't work without say VPC or EC2 availability.

I think that's all GP meant, it just reads a bit funny, not that it's wrong.

Yup, they didn't mention it by name, it was stated as "our upstream provider".

something about antifreeze in the dogfood