When your Arch-Linux oath collides with macOS provisioning reality

Description

Top half: white background with black text that reads, "I'm not an Apple fanboy but I still own a macbook as I develop apps for mac and iOS (personal and company) It's still weird for me to use it everyday It feels like I'm betraying my younger self who promised to never leave Arch Linux with i3WM in a Ryzen 5 APU." Bottom half: a two-panel reaction meme of a bald man filmed in selfie-mode, looking conflicted; a subtitle at the bottom right (partially cropped) reads, "...choose a path from which you cannot return any..." The visual punchline juxtaposes the pragmatic need to ship iOS builds (requiring Apple hardware) against a past self’s purist devotion to a rolling-release Arch box with a tiling window manager on a Ryzen 5 APU. The meme captures the perennial trade-off senior engineers face between ideological tooling ideals and platform-driven client requirements

Common Tags

Apple Macos ArchLinuxUserRepository Linux DeveloperHumor DevEnvironmentSetup DeveloperErgonomics RelatableDevExperience

Comments

Anonymous ★ Top Pick Switching from a custom-compiled i3 config to macOS feels like aliasing “pacman -Syu” to “softwareupdate” and hoping nobody notices the sudo

Anonymous ★ Top Pick

Switching from a custom-compiled i3 config to macOS feels like aliasing “pacman -Syu” to “softwareupdate” and hoping nobody notices the sudo
Anonymous

The real tragedy isn't switching to macOS - it's discovering that after years of customizing your i3 config to perfection, you're now paying $99/year for the privilege of distributing apps through an ecosystem where you can't even change the default terminal shell without disabling SIP
Anonymous

The real tragedy isn't leaving Arch Linux - it's realizing that after years of meticulously configuring i3wm keybindings and maintaining your dotfiles in a git repo, you now spend your time arguing with Xcode's interface builder and waiting for Swift compilation. You've traded the philosophical purity of 'I use Arch btw' for the pragmatic resignation of 'I develop for iOS because that's where the money is.' The path from which you cannot return isn't macOS itself - it's the moment you stopped caring about your window manager and started caring about App Store review times
Anonymous

Arch purist pledges eternal pacman loyalty - until Xcode demands 'sudo reality check' on M-series silicon
Anonymous

Eventually I learned that xcodebuild is a transitive dependency of revenue; the resolver is brew install macbook && fastlane codesign
Anonymous

You think you’re immune to walled gardens until a provisioning profile makes Xcode the only window manager that can ship revenue
@puresera 1y

I also have a mac... with arch installed on it
1. Deleted Account 1y
  
  ntr
@H3R3T1C 1y

I also have a mac only from work, the only App that has is Kitty at full screen.....
@casKd_dev 1y

running a macOS vm ain't hard, all you need is ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc
@Le_o_R 1y

I have a Mac for work. I work remotely, so I end up using my personal laptop with an Arch fork for most of the stuff.
1. @RiedleroD 1y
  
  which arch fork?
  
  @Le_o_R 1y
  
  Artix.
  
  @RiedleroD 1y
  
  neat ^^
2. @dsmagikswsa 1y
  
  no VPN restrictions?
  
  @Le_o_R 1y
  
  When I'm on VPN I use the Mac. But I don't need to be on VPN to use AWS. And we barely have on-prem stuff anymore.
Deleted Account 1y

He become the very thing he swore to destroy