My Linux challenge: Part 2 Apples and oranges
It’s been over a week since I challenged myself to use desktop Linux for my development environment. My reasons were simple: my Intel MacBook Pro is struggling with my workflow, and Apple’s prices and practices are putting me off buying a new Mac. Before shelling out on a new machine, I wanted a serious look at the alternatives, so I repurposed my barely-used gaming desktop to run Pop OS.
Thus far, it’s been a pleasant experience, albeit some differences might take time to get used to. I migrated my workflow without issues as I primarily work with Python, Node and Docker, which run fine on Linux. I also swapped my tools for FOSS-friendly alternatives, replacing VS Code with VSCodium, Postman with Hoppscotch, Chrome and Safari with Firefox, and TablePlus with DB Browser for SQLite.
Moving from a Mac laptop to a PC desktop means more fan noise and higher energy consumption, but I have a serviceable machine I can upgrade as needed. A few days ago, I doubled the memory to 32 GB for a mere $69 Australian, a fraction of the cost of Apple’s BTO upgrades. Coming from an ecosystem where everything is soldered or glued down, the freedom and cost savings are quite refreshing.
Moving from macOS to Linux means I have to learn new keyboard shortcuts and no longer get iMessages, but I claw back a lot of performance. Admittedly, comparing a desktop to a laptop isn’t fair, but Linux runs much leaner than macOS, thanks to fewer background services running by default.
After a week’s coding, my initial impressions are that I’m facing trade-offs rather than deal-breakers. Desktop Linux has come a long way since I last used it, but its advancements aren’t at the expense of performance or user freedom. Pop OS feels built to get work done as efficiently as possible, with minimal distraction and friction. macOS hasn’t felt like that since Snow Leopard.
