Hah yeah I spoke to Jon about this stuff at KubeCon. I said something like “Try to keep up!” :)

Lots of common tooling in this space though and getting more attention to open models can only help.

The terminal motd tells you exactly how to use the packages involved when you open it.

Just about everyone who has made meaningful contributions to Bluefin are tinkerers. The entire stack is designed to tinker and customize.

It’s one command in Bluefin, same as everything else.

brew install btop vim

https://docs.projectbluefin.io/command-line/#installing-applications

I feel like they don’t take the time to think things through and throw together. Instead, they throw together a new thing to address the shortcomings of the previous five things.

This is a weird statement it’s designed this way on purpose. You seem to be looking for “one package manager to rule them all” in a world that’s purposely splitting things up.

You can always just get the status updates directly from the project: https://universal-blue.discourse.group/t/a-brighter-future-for-bazzite/11575

All the supported IDEs in bluefin are brew packages and tailscale is included.

No idea on the selinux stuff though.

My thesis is essentially that we’re creating too many package package managers with too many compromises.

Your issues appear to be config/documentation related. What apps am I missing out on by not using system package managers?

package managers, you can do essentially anything.

Yeah, like break your computer, no thanks. :)

No they would brew install neovim. System-level package management goes away entirely, that’s the point.

What new package managers? homebrew has been around for years. What problems are you describing? If you mean read only root that has been around since the 1980s. The problem as you describe it has been removed, you move on from package based entropy to image based systems.

This isn’t a trend, modern linux is this way, it’s just the desktop that has been behind until now.

Bluefin maintainer here, you’ve described how Bluefin works except it’s ~/.local/bin.

I am pretty sure we have not been developing package managers lol.

You’re doing it the correct way, usually the people who are confused are used to their existing linux ways. You only have to learn this way and that will not only be best practice but works on any linux distro.

The immutable gimmick that’s currently going on right now is still way too flavor of the month for new users who are trying to learn from a ground set of nothing.

New users aren’t going to administer their computers either. there’s no “flavor of the month” it’s just teaching new users how to administer linux systems properly. And of course directions on the internet are going to be incorrect, the only correct solution is to follow the documentation, not random guides on the internet.

It’s an image, there’s no such thing as “left all over the place”. Source: I’m one of the maintainers.

https://github.com/orgs/ublue-os/packages

All of the affected files are in the user’s home directory, not on the system.

The dotfiles between GNOME and KDE are the same, the base image doesn’t matter, if you try to switch DE’s on old distros you have the same problem.

Bluefin comaintainer here. The metrics are flathub and app developer donations, not the base image. You spread the love when you install a flatpak or buy a linux game and make those numbers go up.

The idea that the base OS is important isn’t a thing, the only way to fix the economics of the linux desktop is to focus on applications, not distros.

back to a normal Linux.

What’s normal linux?

What’s stopping you from turning updates off?

Bazzite contributor here, there’s no reason to care about this. This term just confuses people you can safely ignore it.