Tried Arch for the first time | My experience and impressions
I used linux intermittently in the last 15 or so years, migrating from early Ubuntu versions, to Manjaro, Pop!_OS, Debian, etc. And decided to give Arch a try just recently; with all the memes around its high entry point, I was really expecting to struggle for a long time to set it up just as I want.
Disclaimer: your mileage may vary. I’ve been using some sort of unix CLI since the time I learned to pee standing (last year?), and in case of Arch this prerequisite makes the whole process a lot simpler.
Learning curve
The installation process itself was quite simple. Perhaps the most complicated part was the disk partitioning and setting up the bootloader, as I’ve never done it myself. But then again — on any other OS you kind of have to do the same, except maybe through the GUI and not CLI.
One thing you quickly learn when using Arch — is you always should consult their wiki. Actually, “consult” is an understatement; let me put it this way, on the hierarchy of usefulness: there’s reddit, then stackexchange, then random “how-to” websites, then your logic, and then there is the Arch wiki. Exactly in that order, since your logic may betray you, but not the Wiki. Jokes aside though, they’ve somehow managed to document every minute detail, with specific troubleshooting for almost any combination of hardware out there. This is incredible, and as a person who also spends a lot of time writing documentations — hats off to the devs and the community.
Once you learn how the daemons work, how pacman and AUR packages work — the rest is actually quite similar to any other OS. Except that Arch, even with a bloated DE is frigging fast and eats very little battery. I actually use CLI package installation also in Windows (winget) or MacOS (brew), so learning to use another package manager was not too steep.
Drivers
The main caveats actually come when you want specific drivers for your specific hardware. For instance, the out-of-the-box drivers for my laptop speakers were horrible, with the sound seemingly coming from someone’s redacted (never checked, perhaps it was). But that could quickly be tweaked with the “pipewire/easyeffects” with custom profiles which you may find on the web.
GPU drivers were not really that much of an issue for me (if I actually read the wiki properly). Enabling GPU acceleration in some of the apps (like Blender) required the AMD HIP toolkit installed (they have Arch support) with some minor tweaks in the Blender configs. Similarly, the camera, mic and bluetooth drivers were available as AURs or even native pacman packages.
Caveats
Caveats that come with Arch are actually shared among almost all linux distros (or more specifically — DEs). Support of Wayland, while improving gradually over the years (with a great leap forward in Plasma 6), still sucks majestically. Luckily, for many of the most popular apps (slack, zoom), there are third-party AUR packages supporting Wayland natively (I spent a lot of time looking for exactly that on Debian with no success)! All of the apps I needed I actually found with the Wayland support in AURs, but, again, your mileage may vary.
Takeaways
I’d say if you just bought a fresh out-of-store laptop with no data on it to worry about — you should definitely give Arch a try, even if you’re a beginner. Once you fail a couple of times (like I did), you’ll not only learn a lot more about the behind-the-scenes working of your own computer, but will end up having one of the fastest and efficient OS-es out there, which you will now be able to configure to your exact liking.
Unfortunately, I’ve never been able to really daily-drive Linux (and this Arch experiment is no exception). Don’t get me wrong: I love linux and the idea of having independent open-source and infinitely customizable OS. But unfortunately I professionally rely on some of the apps, that have no viable alternatives for Linux (PowerPoint, Photoshop, Illustrator, Proton Drive).
PS. “but what about GIMP, or Krita, or Inkscape, or OpenOffice, or using rsync for cloud storage, or <YOUR_FAVORITE_TOOL>?” you may ask. Trust me, I tried it all. Every last presentation, raster/vector graphics software out there. Regardless of how much I hate Adobe, their software is top tier, and until GIMP becomes the Blender of graphic design, I can’t really rely use it for most of my purposes :(
PS. “but what about GIMP, or Krita, or Inkscape, or OpenOffice, or using rsync for cloud storage, or
<YOUR_FAVORITE_TOOL>?” you may ask. Trust me, I tried it all. Every last presentation, raster/vector graphics
software out there. Regardless of how much I hate Adobe, their software is top tier, and until GIMP becomes the Blender
of graphic design, I can’t really rely use it for most of my purposes :(
The Trust me, I tried it all. and mentioning OpenOffice in one paragraph doesn't feel quite right.
OpenOffice is obsolete. Instead there is ONLYOFFICE and LibreOffice as open source choices for Linux users, available as Flatpak, Snap and probably AppImage.
OpenOffice is dead since years, Libreoffice is what is used today :D
Btw Inkscape is said to be quite good. GIMP 3.0 will have color profiles and nondestructive filters.
I used Libreoffice Impress instead of Powerpoint recently.
you will need to learn the core concepts new, master slides etc.
once you have your own templates, presentations will be very nice
you dont get AI bullshit templates so more manual work but more authentic presentations
same for hunting down icons, stock images etc.
for collaborating OnlyOffice is used, integrated into Nextcloud. OnlyOffice has a Desktop Client, but I dont see the reason, Libreoffice is more feature complete.
I am really curious to see what happens with GIMP when they finally release 3.0 ( before May hopefully ).
3.0 will introduce CMYK, non-destructive editing, and other pro-level features. So it will be interesting to see if more people suddenly find that it is a viable Photoshop alternative.
Even more interesting potentially is that nee features can actually ship. It has literally been years now that new ideas get lost in dev versions that nobody uses. Going forward, improvements can be added to stable releases that people will actually use. It could be a game changer for the project.
As a casual Linux user this confirms exactly what I always thought about Arch: there are significant benefits that I would appreciate but I cannot afford the time and energy investment.
If I didn't have a job, I would absolutely make it happen. But in the limited time available to me I just have too many other things I'd rather be doing
I just switched to Linux for the first time last year, and I've been using EndeavourOS, which I've been told is like Arch with training wheels, and my experience has been fantastic. In case anyone wants a slightly easier way to peek at Arch.
Try donating projects you would like to use. If your adobe subscription amount is going to gimp and inkscape, you are buying yourself into the future of freedom. If you buy adobe, you will limit yourself more and more.
Unrelated - I love that picture. I want it as a wallpaper but it's way too square. Do you have some source where I could get a higher definition, wider and/or taller version?
I had the same experience. Despite all the doomsaying online I found the installation and configuration process pretty straightforward thanks to the quality documentation.
Unfortunately, I’ve never been able to really daily-drive Linux (and this Arch experiment is no exception). Don’t get me wrong: I love linux and the idea of having independent open-source and infinitely customizable OS. But unfortunately I professionally rely on some of the apps, that have no viable alternatives for Linux (PowerPoint, Photoshop, Illustrator, Proton Drive).
There are viable alternatives for Linux as you mentioned. But non are going to just be drop-in replacements for those tools. There are a lot of graphics design tools out there now that are just as powerful as Photoshop for what most people need. But the big issue is they are different in just enough ways that it can be a challenge to switch to them once you are used to the way Photoshop and the other windows only tools work. This is just something you are going to have to get over if you want to try Linux longer term.
But it can be far too much to switch all at once and with a completely new OS as well. So don't. Instead start using these tools and alternative on your Windows install now. Start trying out different ones (there are a lot, both open and closed source), and giving each a decent attempt to use. Start out with smaller side projects so you don't interrupt your main workflows and slowly over time start learning and getting used to the different way these other tools work. If you make some effort to do that while on Windows then the next time you try out Linux they wont seem as bad. But if you keep sticking with Windows only software on Windows you are going to find the same issue every time you try to switch.
Same for me. Arch is great and I'm happy with it, but I need MS Office (I know about Libre Office, but there are files that are made in MS Office and I have to work with them) and at least CorelDraw (at least until SVG spec allows tab characters in text objects) to fully work in Linux. Until then, I have to use Windows :-(
I’ve been using some sort of unix CLI since the time I learned to pee standing (last year?)
Well, if you're a woman that's a huge thing, pee standing!
If you're a man, pee sitting (at home/friends home), please... It makes cleaning very, very simpler and the bathroom doesn't smell like public restroom
Where would one find custom Pipewire profiles for specific speakers and would those work for an unwashed Mint peasant like me? I have external speakers for my PC but the sound has room for improvement. I tried tweaking with Easyeffects but that is not really that easy if you have no idea about sound engineering.
Excellent work - I currently run Endeavour on a PC and laptop. This article has almost made me brave enough to try a bare bones build of Arch on the laptop :-)
My Linux usage was: Ubuntu, then Arch, then I got tired of it and took a break from Linux. I found Fedora KDE in 2017 and been using it ever since. Only reinstalled once to switch to btrfs and it went surprisingly smooth.
I like Arch, and I love the wiki, but I appreciate sane defaults and ease of use. I'd rather optimize down than pull features out of repos.
Another distro I'd check would be Suse, or one of the immutables, starting with the Fedora KDE one. When I have time for it.
I have a windows VM to use Affinity (Photo, Publisher, and Designer), a Pro level suite that will be fine for most work, and is pay once, not subscription.
It's not as heavy duty, but the layout/tools are pretty much the same so it feels significantly more intuitive of you're used to the PS way of doing things than Krita, GIMP, etc .