When things get dire, the fast and high bandwidth Internet we know will be gone, but a form of slow, intermittent Internet will probably be around; still technically an Internet.

And the back button will break the entire app.

Oh, so that’s why Google is killing sideloading.

Then again, I could have accomplished the same thing by knocking off work for the day and going to the driving range.

Hey, look at the bright side, as long as you were chained to your desk instead, that’s all that matters.

uninformed for skeptical

Perhaps one begets the other.

The article is not fishy, you are just uninformed. They are powering the datacenter with turbines fueled by natural gas. You are right about the datacenter though, it’s beyond fishy, into crime territory. To top it all off, they have approval to run only a handful of turbines (after not even seeking approval in the first place, i.e. running them illegally), but they are running a ton of them.

Gary explains why.

I feel there’s a certain sad irony about the domain on that link.

I am having flashbacks to the scene in Idiocracy where the doctor is talking about his wife.

The P stands for plunder.

That’s great, thanks! I really appreciate the detailed response and the links.

The methodology IS cloud native

Ok great. Is it also fair to say that cloud native is the methodology? Or is cloud native a higher order concept that the methodology can fall into? I.e. rock is music, but music is not rock.

Dude, thank you for this. IMO reducing that down to simply “cloud native” is doing a disservice to how absolutely cool that methodology is.

I loved RancherOS in the server space, and always wished there could be a desktop version of it, but I realize that the isolation of docker on docker would be very difficult to deal with for desktop applications. From your description, I feel like Bazzite has done the next best thing.

If I may frame things in RancherOS terms and perspective briefly, given your description of what’s going on with Bazzite, the System Docker container image is being built in the cloud every day, and you could pull it down, reboot, and have the latest version of the OS running. The difference, I am gathering from context, is that while RancherOS “boots” the system image in docker, Bazzite simply abandons RancherOS’s hypervisor-esq system docker layer, and does something like simply mount the image layers at boot time (seeing as how the kernel is contained within the image), and boots the kernel and surrounding OS from that volume. The image is simultaneously a container volume and a bare metal volume. In the cloud, it’s a container volume for purposes of builds and updates, which greatly simplifies a bunch of things. Locally, the image is a bootable volume that is mounted and executed on bare metal. Delivery of updates is literally the equivalent of “docker pull” and a boot loader that can understand the local image registry, mount the image layer volumes appropriately, and then boot the kernel from there.

Do I have this roughly correct?

As someone who builds and deploys software in the cloud all day, seeing the term “cloud native” used for a desktop OS just reads as jibberish to me, no offense. Nobody can seem to explain clearly in simple terms what is actually meant by it.

Does it just mean all of the compilation of binaries and subsequent packaging have all been designed and set up to run in a uniform build pipeline that can be executed in the cloud? Or is bazzite just basically RancherOS (RIP) but for the desktop? I am seeing people in this thread talking along the lines of both of these things, but they are not the same.

Can you explain what the term “cloud native” means as it relates to bazzite in a way that someone who can build Linux from scratch, understands CI/CD, and uses docker/kubernetes/whatever to deploy services in the cloud, could grok the term in short order?

Why have it do everything?

Isn’t the guy behind systemd a (former?) Microsoft employee? I feel as though that might offer a clue as to why the trajectory towards bloat.