For starters, in case you’re not aware of what
ChimeraOS is, it’s an Arch-based Linux distribution that’s designed to run Steam’s Big Picture interface on startup. The idea is you can transform your desktop PC into a console by having a controller-driven interface, without ever needing to connect a keyboard or mouse. Basically, it was the much-needed spiritual successor to the old SteamOS 1.0/2.0, that got rid of
a lot of the headache that came with SteamOS prior to version 3.0. It also provided an enhanced experience with things like the
Chimera web app, which allows the user to add ROMs and certain Flatpak applications with another device connected to the same network.
ChimeraOS also comes with enhanced security by keeping the core filesystem immutable. Updates to ChimeraOS – things like the kernel, the graphics driver, etc. – are handled entirely by the ChimeraOS team and not the end user. This allows for curated packages, ensuring they’re properly tested and working before they are shipped to the end user. If something goes wrong, it’s usually because of the ChimeraOS team, not the user.
That being said, users
can still make use of their own software through the use of Flatpaks. These Flatpaks can be added through the aforementioned Chimera app, or by using the GNOME Software Center in Desktop Mode. Users can also unlock the file system via a terminal command, and install packages with pacman.
Sound familiar? That’s because that is pretty much what SteamOS 3.x does. Like ChimeraOS, SteamOS 3 is based on Arch, uses an immutable file system, and makes use of software outside of Steam via Flatpaks. So here’s an interesting tidbit that I’d like you to know:
the ChimeraOS team were the first ones to implement this idea. Valve quietly copied these ideas into SteamOS 3, without ever acknowledging the ChimeraOS team. It seriously makes me wonder what SteamOS 3 would have been like if it weren’t for ChimeraOS. ChimeraOS founder, Alesh Slovak, even
hinted at this when I interviewed him back in April.