i know 2021 feels like a lifetime ago, but AWS had linux (Amazon Linux?) a decade before that (maybe even 18 years ago?) When i think "azure" i think AD, winserver DCE, and so on. Obviously if they want complete vendor lock in they have to have first party linux, too, rather than people doing hypervisors on VMs on hypervisors.
i used to call myself a "cloud engineer" 14 years ago, me and a friend developed a formal way to deploy thin clients using AWS as the host, and it worked well for everything including youtube videos. this was in 2009, we had both been working with AWS since the first "public" instances became available.
So i suppose when azure was announced and came out, i was acutely aware of what they offered, and it was, you know, marginally cheaper than the AWS windows servers, as azure didn't have to pay microsoft as much for DCE licenses, maybe.
But it makes sense they have Linux now, as i said, ecosystem lock-in...
Are you sure about that? Everything I can find now and from when it was first covered suggests that it's an RPM based "distro" (let's not argue about whether it's technically a distro).
The TomsHardware article you linked to in turns links to ZDNet which in turn links to an InfoWorld article (isn't modern reposted rehashed "news" slop just fucking delightful) about the "release" of CBL-Mariner notes that it was created as a replacement to the then-recently-deprecated RedHat CoreOS, and references that (at the time) MS had a deal with a company that was supporting a CoreOS fork.
Given those two factors, it isn't impossible but it seems hard to believe that they would use a Debian base but then Frankenstein RPM package manage into it.
reply