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?
Hey there, I'm the founder of Bazzite.
Hey man, so great you are here! What an opportunity that you came here to provide clarity. Thanks for being here!
Just wanted to confirm that we have no interest in VC funding. we're [not] marketing to people with too much money and a lack of sense
That's super great to hear. Refreshing in fact.
Putting a whole distro together is a monumental task. Why have you gone to all the effort to do so? What does Bazzite bring to the table that can't be found by using any other distribution? For everyone who is currently using, say, fedora, why should they all switch to Bazzite today? (I am currently running fedora and I am thinking about a change, can you give me a reason to jump?)
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?
Tell me you are too oblivious to implement CI/CD without telling me you're too oblivious to to implement CI/CD. Their builds and packaging should have been fully automated if it was such a pain. If you can make a Mac version of any software, you can make a Linux version. The debate internally was likely management being dumb as rocks and overruling anyone who actually knows anything.
Might be this dude; it is not free, just very affordable in their market. It turns out making it affordable also brings in a lot of revenue.
O.C.: Have you consulted about this “tables” approach with other Lua developers?
I.T.: After that, I went back to Dmitry and asked him if my understanding of “everything is a table” was correct and, if so, why Lua was designed this way. Dmitry told me that Lua was created at the Pontifical Catholic University of Rio de Janeiro and that it was acceptable for Pontifical Catholic Universities to design programming languages this way.
Lol what? Is there some kind of inside joke about Catholics and tables?
Interesting. I wonder how that compares to a similar Li-ion cell. Also it's a shame there wasn't a close-up on the markings of the battery in that video to know what it is exactly. I don't imagine all cells are equal.
The battery packs from the article, for instance, are not constructed from cylindrical cells, but from large thin and flat square cells. The cathode material appears to be unique as well, as far as I can tell; who knows what's in those blue cylindrical cells.
explosive hazard
Can you elaborate on that? I was just reading the data sheet for these batteries, and these are tested with a ballistic penetration test, resulting in no fire.
I'm presuming this concern is from watching videos of elemental sodium reacting with water, which stands to reason, but I've not heard of exploding batteries
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.
Howie Mandel origin story?