I agree in the case of Fedora Atomic, they’ve stuck to flatpak and podman (so far, they have their system extension manager tool in the work) and have rpm layering as a fallback.

But not all atomic distros have that fallback. Universal Blue, more specifically Bluefin, does not want to allow layering at all; this is already implemented in the LTS version (though it’s just bootc, so you can build your own image to install rpms). This is also true for “distroless” models like Gnome OS (and there you don’t have any prebuilt packages to pull in even if you made your own buildstream image). So for these, you have to make-do with the package managers they provide or you’re out of luck.

In an ideal world, I think we should have a single package manager that sits on top the the OS that can handle everything: GUI apps, CLI tools, sandboxed by default but also able to be disabled completely for the apps that don’t work well with sandboxes. The closest thing we have to that right now is snap.

In an imperfect but more likely world, I would be fine with two package managers. Flatpak for GUI apps and something else for CLI tools. “Flatpak Next” could fix one issue with its unsandboxed mode. But I still haven’t found something that universally works well for CLI apps.

• Podman is the classic answer, but it can be a bit annoying jumping into and out of boxes. Doesn’t work well for more “system tooling” like Tailscale that also want services.
• Homebrew is a more modern suggestion and actually works pretty well. But I’m not a fan out how hijacks PATH in a way that can break OS packages (such as by making homebrew dbus and systemd used over OS versions). And last I tried, the homebrew version of tailscale didn’t work (though I have read that others did get it working).
• Coldbrew is an interesting alternative to coldbrew, which uses alpine packages and doesn’t mess with PATH directly, but it does place some stuff in .local/bin that could end up overriding some binaries anyway (though not to as high a degree as homebrew, and thankfully doesn’t affect libraries). But has integration issues due to sandboxing (personally had an issue where I had an app that wanted to open my browser, but it couldn’t see my browser because of the sandbox).
• I still need to test Nix on an atomic distro

When something as fundamental as git requires multiple obscure commands to install, you’ve got to think twice about the target audience.

Ideally the tooling gets better and you don’t have to do anything else but “toolname install package” or have a declarative list of what to install.

why Linux power users (i.e. most Linux users on lemmy) aren’t suited to immutable distros.

I think the main problem is that immutable distros haven’t thought things through from the beginning.

It started out as just using flatpak and podman. But each of those has limitations. But rather than improving them, we just keep creating / bringing in new package managers. Homebrew, cold brew, system extensions, nix, etc.

Funnily enough, the only entity who is sane in this regard is Canonical. If snap has a limitation, they just update snap to not have the limitation rather than brining in another package manager.

But honestly I think the biggest offender here is flatpak. If not for its mandatory sandbox and anti CLI tool stance, it could have handled everything. “Flatpak Next” seems to be address the first issue as it is planned to have an unsandboxed mode.

Because AIs don’t need salaries, don’t unionize, can work 24/7.

For some tasks, AI has already completely obsoleted humans. An AI can write a shitty PR filled newsletter faster and cheaper than a human. It keeps getting better at certain tasks, like programming.

All AI companies want to be the one that controls the best AI. Because if they do, then other companies will pay them to rent out AIs for cheaper than human labor.

Companies fear falling behind. So they dump loads of money into AI. And currently, investors like hearing about AI. So the more companies say and push AI, it increases investment into the company.

The main problem is that it’s just not battle tested like GNU coreutils are. And Canonical has only tested this in one cycle, 25.10, before introducing it in an LTS. Would’ve made more sense to wait until 26.10.

Other find problem with it being MIT licensed.

I had a couple of problems with the profile manager.

For one, there’s now two profile managers that do not work together. You can’t use an old profile in the new profile manager or vice versa. You can access the old one via .desktop entry or from the CLI. But you can’t access the new one from the CLI.

It’s also a bit buggy. For example, if I have my “Personal” profile open and middle click the Firefox icon, it will open up another “Personal” window rather than show the profile manager. And to access the new profile manager, I first have to aim for a tiny target (especially tiny on my 100% scaled 4K monitor) and do 3 clicks. With my solution, I explicitly choose which profile to use from my dock.

It’s also hit or miss on which window a link from an app will open up in. Whereas with my solution, I can set “Firefox (Personal)” as my default browser and always have stuff open there.

I don’t use openSUSE, but seeing their security reviews tempts me…

It could be improved. Sebastian Wick and Lennart Poettering made comments on how hard POSIX makes it hard to be secure. There are better APIs that try to be safer.

• https://blog.sebastianwick.net/posts/how-hard-is-it-to-open-a-file/
• https://mastodon.social/@pid_eins/116459585811044061

And since uutils is not Linux only, it can’t use these safer APIs directly, or at least not without writing more platform-specific code.

Technically, Ubuntu is behind the curve not at the forefront on this. Universal Blue already includes quite a bit of AI stuff and Fedora has had drafted plans for a while.

Universal Blue: https://hachyderm.io/@jorge/116476967711636491