🛴 Follow me on:
Twitch: https://www.twitch.tv/developedbyed
Twitter: https://twitter.com/developedbyed
Github: https://github.com/developedbyed/

#programming

developedbyed

A developer shares their experience using Arch Linux as their primary operating system after switching from VS Code to Neovim. While praising the tiling window manager and low resource usage, they encounter significant challenges with audio drivers, video editing software compatibility, application availability, and constant troubleshooting. The developer is considering switching to macOS (Mac Mini or MacBook Pro) or dual-booting to regain productivity and access to essential applications like DaVinci Resolve, Streamlabs, and Affinity, prioritizing stability over customization.

Arch Linux...time to say goodbye?

Arch isn’t for the normies, its for the nerdy programmers who can’t handle normies. 👍.

I admit I tried to go in unbiased, though at first the only thing I could think of was “skill issues”, but I’m not that type of guy and I don’t want to be. Then he started talking about some of the most idiotic things I have ever heard, and all my efforts were in vain:
<ul>
<li>“There’s no graphical update tool”: there are plenty, install one.</li>
<li>“I can’t use windows software like Davinci Resolve or Affinity suite”: the only problem would be some video codecs not available for linux in DR due to licensing issues, but then again there’s Proton/WinBoat and a boatload of other ways to do it.</li>
<li>“There’s hissing in my recordings”: either denoise or check your source? Do you have coil whine in the recording? Are you so used to having audio auto filtered that you never checked your sources?</li>
</ul>
I know that when I hear this type of speak coming from what I dub “TypeScript developers” I tend to disregard what they’re saying, but I honestly and genuinely have no idea what their issue is like. You don’t even need to have knowledge on those issues, any random AI knows the solutions. Like, what the heck?
YMMV, I guess…

full control over updates helps you avoid a lot of headaches. it’s rarely the distro itself that causes the problem and most issues can be solved, quite simply, by following these basic guidelines:
<ul>
<li>use btrfs and timeshift</li>
<li>get into the habit of manually creating a snapshot before updates</li>
<li>perform updates manually, evaluating case by case how to handle problematic or critical ones (and, if you followed point 2, you can always roll back and no one gets hurt)</li>
</ul>

Arch is great. I starter working with it a month ago. There are plenty of docs and chat gpt can help with trouble shouting. I agree it could be better with video and graphical setup but it’s general issue for Linux.

I’m not sure why devs in particular think the choice is Arch or Mac. I assume it’s for views when it’s content creation but I’ve worked with people who persist with Arch then claim linux is shit and switch to Mac. How tf do you know you’ve used 1 distro which is notoriously difficult to use and setup and has toxic support forums? There are so many better choices in terms of support out there. My preference is Pop or fedora as I just want to setup and get on with my work. In my experience these 2 distros are quicker to setup and use than Mac and have far fewer bugs.