They don’t. DHH is a rich guy with rich friends. This is just friends donating to a friend’s project to show support.

And that also means that the CEO of 1Password really has no problems with DHH as a person, those who talk about Omarchy being revolutionary/special or anything like that at best have rose-tinted glasses.

I like Fedora Atomic with bootc for this reason. While Nix language is quite confusing and gets even more confusing when you find online advice that has a different setup than you that introduces compatibilities, bootc is just an OCI containers that I can run bash commands in to get stuff set up.

It’s still not one-to-one. Generally, I find that using bash to set things up makes more things easier than harder compared to Nix. Though Nix does make some stuff simpler.

That being said, I haven’t tried NixOS in a while. I’m sure that with a decent LLMs, today its easier than ever to make a competent NixOS config. I’ve been meaning to try, but haven’t found the time.

Debian voted to not ban AI. Proposal E won:

https://www.debian.org/vote/2026/vote_002#texte

Phoronix’s more real world testing didn’t have Gnome performing badly: https://www.phoronix.com/review/cachyos-desktops-july-2026

Doesn’t KDE kinda have that same refresh rate issue on Wayland? I remember seeing a bug that Qt has a limitation in this regard, In the video I saw the workspace transition ran at the lower refresh rate when multiple monitors were used.

Thankfully I stopped using multiple monitors so I can’t personally confirm.

Personally, I wouldn’t recommend Vanilla OS.

• They released v1 based off a non-LTS Ubuntu released and then quickly stopped supporting it while they worked on v2. No security updates.
• They released v2 with no upgrade path from v1. v2 was based on either Debian Testing or Sid. It did not regular receive updates. Right now the website says that last updates were released in January. Presumably they stopped working on it to work on v3.
• I’m not sure if you can upgrade from v2 to v3. A fresh install is probably necessary.
• Mirko founded Vanilla OS but his main focus now seems to be Sinty OS.
• On a petty note, the website makes you opt out of sharing and selling your personal info to third parties.

That’s a lot of churn and issues for such as young project that advertises itself to new users.

Wonder how much of that is going towards Hyprland: https://omarchy.org/news/2026/08/omacom-foundation-to-be-exclusive-hyprland-sponsor/

You absolutely can sandbox using SELinux. Red Hat even has a tool called “sandbox” for just that: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/chap-security-enhanced_linux-securing_programs_using_sandbox

Edit: and Android sandboxing is built heavily around SELinux: https://source.android.com/docs/security/features/selinux

I don’t believe the Steam flatpak is responsible for those issues

openSUSE recently added some more security policies. By default, Wine cannot run normally. There’s a package you can install that sets SELinux security policies to allow it to work. If you install the openSUSE Steam rpm, that security policy automatically gets installed too.

This is a downside of flatpak’s approach to sandboxing. It aims to work everywhere on every distro, using bubblewrap instead of something like SELinux or AppArmor. But it also does not interact with AppArmor or SELinux, so if they block something, flatpak can’t override that.

Meanwhile, snap uses AppArmor for sandboxing. So even if there was a policy like openSUSE’s that prevented Wine from working by default, since snap speaks AppArmor, it can give itself the necessary permissions to make Wine work.

Bazzite uses the Steam rpm, not flatpak.

Though I think other launchers like Heroic may be flatpaks. But that’s no different to SteamOS.

I don’t think so, this still would let them host it so long as don’t have a “competing fork”. I’ve heard of licenses like Server Side Public License (SSPL) that do you what you say. Basically, that license requires all the infrastructure around the software to be open source to. So something like AWS couldn’t host the software without first open sourcing all their infrastructure.

Wayland wants to avoid problems that X11, Windows, and MacOS have. It deliberately avoids some “features” that application developers expect. A lot of it relates to security and privacy.

An example is that a window does not know where it is positioned on your screen and it cannot choose where to place its windows. Personally, I love this behavior. It means I can open an open and it opens in a consistent location (for most Wayland compositors, that’s centered on the screen). But others don’t like that. They would like the app to control where it opens; for some apps (a niche nowadays) you may have an application window and multiple more supporting windows, but on Wayland, they would all just get opened on top of each other rather than being placed around the main window.

The main issue is that old Boxes is based on SPICE. It was/is a Red Hat project, but they stopped caring for it and deprecated it. So old Boxes is built on legacy tech that will pretty much just bit rot over time.

Something strange with the March 2026 results was that it had two new distro entries, “0 64 bit” at 17.60% and “64 bit” at 8%. In April, one of those entries disappeared and the other’s share dropped significantly. In May, both were gone entirely and Linux was back to a more reasonable marketshare of 4%.

Overall probably closer to the truth.

I wish people didn’t obsess over these large numbers as much. Like when Linux suddenly hit 5% on Steam when that was clearly just an outlier and was destined to fall right back down.

One annoyance about Python is that I also have a Mac. By default, it comes with no Python. If you install XCode, you get Python 3.9. And of course you can get the latest version from Homebrew.

Granted, I don’t think Amber would help much in this situation either. macOS comes with bash 3.2 and Amber probably targets a newer version that that. So either way I would need to homebrew install newer versions.

Not a DE thing. In /etc/crypttab, you can point to.a keyfile or password to unlock the disk.

So you unlock the OS disk, and on that now readable OS disk are keyfiles and passwords that then unlock the other disks.

Yes, but still important to keep in mind because it broke release expectations. Pop!_OS used release new versions every 6 months and then stopped releasing new versions while working on COSMIC and now only does LTS releases.

And now that COSMIC is “done”, it’s still not quite clear when they will release 26.04. I actually just found a quote from the CEO of System76 where he said “Future Pop!_OS releases, starting with Pop!_OS 26.04 LTS, will now align with the Ubuntu LTS release timing (approximately two weeks after the Ubuntu release date)” but that obviously didn’t happen.

Pop!_OS gets Cosmic updates before they are even technically released.

Pop!_OS packages are not cutting edge. They are based on Ubuntu LTS. They do keep some packages more up to date than Ubuntu, such as Cosmic, kernel, mesa. But the vast majority of packages are from Ubuntu LTS unmodified.

Pop!_OS has also been lagging in using the latest Ubuntu LTS. They stuck to 22.04 for almost 4 years before releasing 24.04. It’s also not clear when they will update Pop!_OS to 26.04, but that should not take as long as 24.04.

Yes, the packaging mess that Atomic distros cause.

I want a couple of functional things:

• To be able to safely upgrade my system silently, without interruptions, and rollback of necessary
• To know my system is not drifting away from upstream defaults and to restore it to a “factory” state
• To sandbox applications

I’d like to be able to do all that efficiently and cleanly too. Atomic systems generally fulfill those first two while traditional distros struggle, which is why I stick to Atomic distros.

But whereas you can use a single package manager on Arch and get everything (albeit without easy sandboxing), Atomics keep adding more and more. Here’s your rpm-ostree, flatpak, toolbox, homebrew, sysexts, etc.

I find sysexts particularly insulting because they regress so much on traditional packages for so little upside. Doesn’t even have dependency management.

I would wish we would stop creating so many package managers and just focus on improving existing ones.

In a more ideal world we would have something like

• Distro based on Freedesktop runtimes
• Flatpak that officially supports both GUI applications, CLI applications, and even daemons/services
• Flatpak would also be able to reuse the Freedesktop runtimes of the host system