It’s not using the same hardware, this seems to use a special compression chip.
To me this feels more like the benefits of a CPU or GPU upgrade. Things run faster, but not due to software improvements. When people talk about things getting optimized due to the high RAM prices, I think most people are referring to software improvements.
In the presentation, they talk about a compression chip: https://www.youtube.com/live/OPRciCSsdS4?t=2060
Does it count as optimization? For supported hardware, it’s certainly cool. But it’s not making inefficient software better, it’s making better use of the hardware.
None, your current hardware lacks support for this.
A package, meant to run anywhere and be sandboxed.
However, they are only properly sandboxed on Ubuntu. They have some downstream AppArmor patches that haven’t all been accepted. They’re decently sandboxed on other AppArmor distros. Basically no sandboxing on distros that don’t use AppArmor, like Fedora.
Surprisingly, it’s LGPL v2.
It’s almost like Jon Seager just really likes Rust.
It can get run automatically by things like Gnome Software.
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:
I have a positive experience with Reolink. Not connected to internet at all currently.
Not sure if I will. If I do, will definitely try some firewall stuff. Another part of me is considering not connecting the NVR itself, but taking the video stream from the HDMI and somehow making it so I can see that stream from anywhere. Would miss out on alerts that way though.
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.
That’s a lot of churn and issues for such as young project that advertises itself to new users.
Personally, I wouldn’t recommend Vanilla OS.
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.
In another comment, I posted a link to the CRAM presentation that mentioned a chip.
This article also mentions some hardware:
I don’t think it would say that if they meant the CPU was doing the compression.