Comment

Comment on Linux gamers on Steam finally cross over the 3% mark

sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨day⁩ ago

Yeah, that is nice. I won’t recommend EndeavorOS or any other Arch installer/derivative for other reasons (IMO, every Arch user should do the official install process once or twice to have a better shot at fixing stuff later), but I do like that UX.

I wish more distros did it. My distro (openSUSE) does something similar, but I also don’t recommend it because the community isn’t all that good for new users IMO.

source

Sort:hotnew top

Holytimes@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
Your like 5+ years out of date with your preconceptions of arch.

Arch at this point is breaks less from updates than most other options if your using a prebuild like endeavour or cachy.

Fuck even the aur breaks shit less than windows breaks which is literally the bar for stability for your avg normies.

source
- sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
  That tracks since I left Arch about 5 years ago, maybe a little longer, and I used it for at least 5 years.
  
  I used it through the /usr merge which broke nearly everything, and for a few years of stability afterward. But even when it was super stable, there were still random issues a couple times each year. It wasn’t anything big (I’ve been a Linux user for 15 years or so), but it did require knowing what to do to fix it (usually documented clearly on the Arch homepage). This was especially true for Nvidia updates. After switching to openSUSE Tumbleweed, most of those went away, and even the Nvidia breakage seemed less frequent, and if something broke, I could easily snapper rollback and wait for a fix, whereas on Arch I had to fix things because going back wasn’t an option (I guess you could configure rollbacks if you had that foresight).
  
  I just took a look, and it looks like manual intervention is still a thing. For example, the June 21 Linux firmware change required manual intervention. There were others over the last year, depending on the packages you use or your configuration.
  
  That’s totally fine for Linux vets, but new users will have issues eventually. In don’t even recommend my distro, which solves most of those issues, because new user support isn’t there. The main reason I left was because I wanted to switch to btrfs (for snapshot rollbacks), and Tumbleweed had that OOTB so I gave it a shot.
  
  source
  - Dojan@pawb.social ⁨1⁩ ⁨day⁩ ago
    
    The main reason I left was because I wanted to switch to btrfs (for snapshot rollbacks), and Tumbleweed had that OOTB so I gave it a shot.
    
    This is precisely why I went with Tumbleweed as well. I wanted a rolling release distro because having initially gotten into Linux via Ubuntu back in 2007, I didn’t really like the “upgrade twice a year to keep up to date with new features” method. It felt really cumbersome back then, as a regular distro upgrade often brought problems with it.
    
    When I looked into other features I wanted, I discovered Snapper and I was all “that’s the one for me!”
    
    source
    sugar_in_your_tea@sh.itjust.works ⁨1⁩ ⁨day⁩ ago
    Yup!
    
    Here’s my progression:
    
    Ubuntu because I was a noob; got pissed at breakage at the release upgrade
    
    Fedora, because that’s what my university used; got pissed that release upgrades took an hour (since fixed I think?)
    
    Arch, because my coworker recommended it
    
    openSUSE Tumbleweed because of snapper and they had a server distro (had recently set up a NAS and tried Leap before switching desktop to TW)
    
    Aeon on laptop because I wanted to try an immutable distro and it was in the family
    
    I’ll probably switch my laptop back to Tumbleweed at some point and my NAS to MicroOS, but for nos things work fine so I’m not motivated.
    
    source
    -> View More Comments