this post was submitted on 28 Sep 2024
873 points (98.7% liked)
Technology
59342 readers
5042 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've been using a Steam Deck for almost a year damn near daily with maybe 1 OS crash that was largely due to a very unstable game. How is ArchLinux unstable, exactly?
SteamOS is based on arch, but it has major differences. The steam deck's update mechanism is completely different from normal arch Linux.
Arch normally immediately updates to the latest version of every program. This is usually fine, but when a big bug is missed by the developers, it can cause problems.
The steam deck updates a base image that includes all the programs installed by default, and by the time it releases a lot of them aren't the absolute newest version. When valve updates SteamOS they definitely run a lot of tests on the base image to make sure it's stable and won't cause any issues.
SteamOS is also an immutible distro, meaning the important parts are read only. This also means updates are done to everything at once, and if something goes wrong, it can fall back to a known good version.
Not to say arch Linux is unstable (its been better for me than Ubuntu), but SteamOS is at a completely different level. It's effectively a completely different distro if we're talking about stability. I think what they're hoping is this support would allow arch to build out testing infrastructure to catch more issues and prevent them from making it to users.
This is not true though. Arch packages new program versions as soon as they can - for popular stuff this happens quickly but not everything updates quickly. And when they do publish a new package it goes to the testing repo for a short time before being promoted to the stable repos. If there is a problem with the package that they notice it will be held back until it can be solved. There is not a huge amount of testing that is done here as that is very time consuming and Arch do not have enough man power for this. But they also do not release much broken things at all. I have seen other distros like ubuntu cause far more havoc with a broken update then Arch ever has.