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

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.