Skip Navigation

As a capable but lazy user, how much would switching to Arch frustrate me?

I know my way around a command line. I work in IT, but when it comes to my personal fun time more often than not I'm quite lazy. I use windows a lot because just plugging in anything or installing any game and it just working is great.

But support for windows 10 is ending and I should probably switch sonner rather than later, so I'm wondering if Arch would be a good pick for me? For reference, I mostly game and do Godot stuff in my free time.

69 comments
  • Welcome! Coming from Windows myself, I made the jump to Manjaro (It has certain issues and I do not recommend it), then to Arch less than a year after. I have been on Arch full time for around 2 years now. After the initial setup, I have found Arch to be pretty low-maintenance and no harder to maintain than any other distro, hardly requiring more than the occasional yay -Syu --noconfirm in the command line to update things. As someone with less computer knowledge than an IT professional, I think Arch's reputation for being difficult is overblown IMO, and I suspect mostly due to intimidation from the more involved setup process prior to the availability of the install script.

    I don't know if you have any familiarity with Linux already from your work, but regardless of what distro you go with, I would go into it with a mindset that you are learning a new skill. Some things are simply done differently in Linux than Windows and will require getting used to, such as how drives work using mounting points rather than drive letters.

    Realistically, setting things up for the first time often requires additional steps and may not "just work," but when using my laptop and gaming desktop from day to day, it works just like any other OS. Gaming has been great for me generally, and the work Valve has done to improve game compatibility on Linux has been spectacular. Most Steam games do, in fact, "just work" for me.

    In the 2-3 years I have been using Linux, I have rarely had things spontaneously break as many folks seem to worry about, or if I do it is because of companies not supporting their Linux communities, like Discord not pushing out updates on time, or major-event changes like the move to the Wayland graphical stack on KDE 6 which undid some of my desktop customization settings.

  • My 2¢ is that running Linux, you play the role of user and of sysadmin. On some distros you only put on the sysadmin hat once in a blue moon, but on others you're constantly wearing it.

    My Arch experience is a few years out of date; I felt I played sysadmin more than, say, Debian Stable, but it wasn't too onerous. I also had an older Nvidia card, so there were some...fun issues now and then.

    I use Debian on my machines now, and am happy. Try some different distributions! Even better, have /home on its own partition (better yet, own disk) --- changing distros can be nice and easy without worrying about your personal data.

    • I tend to agree, but I also don't see it as a fault of Linux/Arch. If you're not the sysadmin for your own system, who is? I'd rather do it, assisted by the collective knowledge of the community, than have Microsoft do it for me. For the last few years it's only required a handful of interventions, with the vast majority of time being spent on initial setup and (re) configuration rather than fixing bugs or addressing breaking changes. So IMO it's more of a test of your personal willingness to invest time into learning and building things than your ability to diagnose and solve technical issues.

    • I don't mind being the sysadmin of my own machine (I prefer it, in fact). It's just that I don't want to spend free time troubleshooting some obscure problem specific to my build because I chose an ASUS motherboard and I don't have drivers for my wireless headset or something. At least not when I'd rather unwind playing a game.

    • If you’re already an admin at work, you might not want to do any system administration at home. Well, until you find out that Microsoft is making some obnoxious decisions on your behalf, that’s when you suddenly find the motivation to do some research and tweak a bunch of settings. Situations like that will also lead to frustrating moments when you find out that your hands are tied, and you end up looking for workarounds. Spoiler: It doesn’t get any nicer after that.

      On the other hand, if you’re running a system that requires you to take responsibility, a lazy admin will end up in frustrating situations too. It’s not that simple to balance these things. You need to know what your priorities are and what kind of sacrifices you’re willing to make.

  • if you use the archinstall to setup everything (partitioning, locales, de's, etc), not that much, but def. more than some "everything and the kitchensink straight out of the box" distros. The installer worked nicely on 2 machines I've tested it on, a laptop and a desktop. While the base system and graphical desktop installed nice, there was quite a bit of manual tinkering left.

    But, steam works more or less the same on linux as it works on windows - but there is some proton version selecting, and even then absolutely everything doesn't work.

    Personally, nvidia+wayland (and xwayland in general) is pretty horrid with some games, but supposedly that's supposedly getting fixed next month... It's always something and the fix is so tantalizingly close.

    and, it's not like the EOL for win10 is that close, seems to be October 14, 2025, so there's still plenty of time.

  • I was an Ubuntu WSL user and installed Arch Linux on my laptop without the install script and it took me a whole day plus a few more hours in the following days (reading the wiki and such). I learned a lot and it was a lot of fun.

    I installed EndeavorOS on my desktop and it was.... Weird. It was so weird that I broke things and had to reinstall it twice. Endeavour is great but I had already gotten used on setting things up by myself.

    I have both computers running perfectly since then but you need to keep in mind that you'll be responsible for doing maintenance on your system. Updating, checking logs, reading and rereading the arch wiki.

    I wish I had tried getting into Arch sooner but I wouldn't recommend it to anyone that isn't willing to dedicate to it. Maybe try Endeavour and see if you like it?

  • I mean maybe? Arch is fun as a project, but imo it's not very fun if you're looking for a stable daily driver without fuss.

    If you enjoy spending an evening tinkering with your config and installing various workarounds, arch is the perfect playground for you, but if that annoys you then I'd suggest looking at more stable established distros, at the very least until you start to get bored by stability. Personal pick is debian, but if you're coming from IT you could install a distro you're already familiar with like alma or Ubuntu.

  • If you're new to Linux, I would reccomend fedora if you don't want to have to fuck with anything, but if you work in IT, you will inevitably want to fuck with stuff more, and arch is great for learning

  • Arch is like buying a Lego and putting it together versus an action figure. If you don't enjoy putting together the Legos then what's the point?

    You should probably go with a ready to use distro

  • As a lazy Arch user, I can tell you that there will be frustrating moments, but not that many. Mostly you’ll be fine, but be prepared for minor annoyances.

    Features

    If you didn’t install it, it’s not on the system. That’s good for a minimalistic system, but frustrating for a lazy admin. Once you’ve ironed out all the issues you encounter during the first few months, the system should be pretty solid and worry free. However, once you encounter a new situation, you have to do your research, and install (and maybe even configure) that one missing thing. Later down the line, this becomes increasingly rare, but never disappears completely, so be prepared for minor annoyances like this.

    Interventions

    Before updating, check the official site for big news. Some rare updates require intervention, so you should know what you’re doing before updating your system. Usually it’s totally fine, and you can run the update command blind folded. It’s definitely not recommended, but it’s not going to destroy a simple installation any time soon. If you do complex stuff with your system, the updates become more frustrating. However, once you break your grub this way, you’ll learn to read those notes before updating. These things don’t happen often, but once a special update like that does roll out, you’re going to find it frustrating. Could take a few years, so you don’t really need to worry about it today. Just know what you’re getting into.

    Updating takes a while

    I update roughly once a week, but occasionally only once a month. Maybe there’s something wrong with my connection or settings, but I get timeouts all the time. As a result, I ended up just using the no timeout option instead of actually doing my research and looking into this problem. Need to take that deep dive one weekend eventually. One month worth updates is also a lot of data to download, and I’m getting 0 kb/s for several minutes at a time, so it takes even longer. A lazy admin suffers from annoyances like these. Be prepared for something similar to happen to your system sooner or later. Probably takes only 30 minutes of reading and two commands to fix, but I’ll get around to it another day. Before anyone asks, yes, I’m using a list of the fastest servers, and no, I haven’t updated that list in months.

    I still have Arch on my main laptop, but recently I replaced the Fedora of my HTPC with Debian. I just can’t be bothered to spend a minute on system maintenance, so Debian is better suited for that purpose. I’m still going to stick with Arch for reasons I don’t even fully understand. Probably just sunk cost fallacy at this stage…

  • The arch iso offers a install guide nowadays (archinstall), so nah not that much.

  • Well, it depends on what you want from your OS.

    If you want games to work with as little bother as possible then a gaming distro might be a better option. The only distro I tried where games JUST WORK on their own is Nobara. They have lots of patches to make games actually work. If you want to play Windows games on steam then be sure to install It's made by the same guy that makes ProtonGE, which you should definitely install if you want to play Windows games on steam, whatever your distro (if it's not Nobara, you can use ProtonUp-Qt to avoid having to install it manually).

    Some games just won't run on any of the distros I tried except Nobara. I'm sure you could get them working fine on Arch or any other distro with some work... but that's work. When it comes to gaming I don't want to go in computer wizard mode, I just want to ride dinosaurs. (Yes I realize the irony of saying that after ditching Nobara on my gaming pc because I would rather have Arch with some games not working than Nobara with everything working)

    Other than gaming I'd say it depends if you like being forced to do things yourself.

    I'm a very lazy woman who switched from Windows 10 less than one year ago and tried several distro before ending up with Arch, and it is absolute heaven compared to Windows.

    Lots of stuff don't don't work on my computer, but not because Arch is broken, I just haven't got around to configuring them (lazy + adhd) or I tried but failed because I have no clue what I am doing (four months on Arch for a grand total of eight on linux, so that's to be expected). But I prefer it that way. When I really need a feature it forces me to learn how stuff work, and that was the point of installing Arch instead of a distro that would do everything for me. I've learned a dozen times more in four months on Arch than in the same time on other distros. Or in 25+ years on Windows... I've still got a long way to go and there are lot of stuff that I can't get working yet (looking at you Wayland portals >_<) but I really like it and I don't think I'll switch (though I'm very tempted to try Nix...).

    It you do decide on Arch, please don't listen to people who insist that you shouldn't use the archinstall script because the only "right" way to install Arch is to do a manual install. They're morons. The script is a great way to have a working Arch install quickly and easily, so you can actually use Arch and see if you like it. There's a lot to be learned by doing a manual install, yes. But it's ridiculous to ask people who really want to use Arch to keep using other distros for however long it takes them to learn enough to do a manual Arch install, when they could just use the script and do the same learning while using Arch. If you want to do a manual install go for it, but pressuring people into it is just stupid.

  • As a Mint user who just starting test-driving Arch: once you get through the installation the switch isn't at all difficult. Now,t hat having been said, the installation can have some frustrating moments depending on how you go about it.

  • I'd suggest you give this article a read. If this does sound appealing to you, go right ahead. If you think you'd be frustrated with having to make all these changes, Arch likely isn't something for you.

    • This is just not true at all. This level of configuration is in no way required for having a good usable system. Things are as hard as they are plus how hard you make them.

69 comments