The issue with them right now is there’s no update mechanism. If you use something as a system extension that depends on a library in the image, and that library gets updated, you could have an unbootable system or at the very least a non-functioning application until you can update your system extension manually.

Ideally that update mechanism needs to be a part of bootc so if your system extension is part of your boot process it can be updated ahead of time before the image is loaded.

We’ve looked at it since it’s inception and it’s something we really want, it’s just nowhere near ready yet.

I also said ublue is free to do what they want

Thank the lord we have your permission

They should be scared, we’re here to replace their 30-year failed experiment with tech that’s already successful everywhere Linux makes money.

No they have CUDA. The open driver from Nvidia just means the kernel module has an open source license. They are still the same proprietary pieces of shit that you know and love from a user space perspective.

I disagree with you fundamentally, if it wasn’t for the simple updates and stability this would not have the success that it does. The image is part of the model.

It offers a straightforward onboarding process because it’s image based. The model is part of the success.

Only on Aurora, we don’t ship that.

You don’t use the terminal to do updates, updates are automatic by default.

We also completely removed discovers ability to update OSTree. It’s never been present in a single build of Bazzite.

This is why I don’t pay attention to people that complain about toolkits. You don’t like the way it looks so you make up absolutely disingenuous points to argue about it.

Yes, we are. It’s exactly why it shouldn’t be done and why Fedora is the only project wasting their time with this.

Second best selling consumer Linux platform on the planet, second only to Android.

One of many reasons we replaced it.