Why I Gave Up On Linux

What prompted the switch from Linux to macOS?

The switch from Linux to macOS started primarily due to the need for better battery life and more reliable hardware, especially for college. In 2013, college-bound and seeking serious productivity, the 13-inch MacBook Air's promise of over 12 hours of battery life was a game-changer. This was a significant upgrade from the limited battery performance and heft of existing Windows and Linux laptops.

Initially, the plan was to install Linux on the MacBook Air, ensuring a familiar development environment. However, Theo soon realized that macOS offered nearly the same development tools and the bonus of running creative software like Photoshop natively. This combination of robust hardware and software flexibility paved the way for the transition, shifting preferences towards a more streamlined and efficient experience on macOS.

How did macOS compare to Linux for development?

• Tool Compatibility: macOS supports Unix-based tools, making it versatile for development. It also runs essential creative software like Photoshop natively, unlike Linux.

• Stability: macOS offers a more stable environment with fewer crashes and compatibility issues compared to many Linux distributions, particularly those that might be on the cutting edge.

• Debugging Tools: Apple's Xcode provides advanced debugging capabilities, making it easier to spot and resolve issues, a functionality that some Linux setups might lack or be less user-friendly.

• User Experience: Out of the box, macOS provides a polished user experience that requires minimal tweaking. In contrast, Linux often necessitates extensive customization to achieve a personalized workflow.

• Ecosystem Integration: Using macOS allows seamless integration with other Apple devices, streamlining productivity through features like Handoff and iCloud synchronization, even though personal preferences may vary.

For a deeper dive into how development environments have evolved and the role of tool compatibility, check our GitHub differentiation article.

What role did internships and professional experiences play?

Internships at Amazon and Twitch had a significant impact on the decision to stick with macOS. At Amazon, the hardware limitations were glaring. Interns were given underpowered machines with outdated specs, which made development a hassle. This led to seeking alternatives, including installing Ubuntu on the provided laptop, which proved to be a relief but also highlighted the limitations and time-consuming nature of constant customizations.

Mentorship experiences at Twitch added another layer of influence. Observing a highly productive mentor who used macOS with minimal customization was eye-opening. The mentor's approach showcased the power of defaults and how they can streamline workflows and improve productivity. This perspective shift, seen through the mentor's efficient coding practices, highlighted the advantages of macOS for a developer experience focused on efficiency over endless configuration.

These professional experiences underscored the value of stable, reliable hardware and a streamlined software environment, tipping the scales in favor of macOS for long-term use. Understanding these dynamics is akin to realizing how mentorship impacts young professionals, shaping their career trajectories indefinitely.

How did iOS influence the switch?

The release of iOS 7 had a profound impact on the transition to the Apple ecosystem. iOS 7 introduced a sleek, modern design language that felt revolutionary and far superior to the customizable Android setups that were common at the time.

A friend’s gift of a fully functioning iPhone 5 served as a catalyst. This iPhone, combined with iOS 7, showcased a level of polish and stability that was hard to ignore.

Gradually, the seamless integration and consistent user experience between iOS and macOS made it clear that Apple's ecosystem offered a streamlined and efficient environment—one that was optimal for both personal and professional tasks.

What are the benefits of using macOS defaults?

Using macOS with minimal customization offers significant advantages. One major benefit is enhanced productivity. MacOS works efficiently out of the box, meaning developers can start working immediately without spending hours tweaking the system.

Moreover, using defaults reduces decision fatigue. Constantly customizing an environment can be mentally exhausting. By sticking to the defaults, you can focus on your core tasks instead of worrying about endless configuration options.

Seamless integration is another key advantage. macOS provides a cohesive and user-friendly experience across different devices, reducing the friction that often comes with syncing and device management. This uniformity supports smoother workflows and helps maintain a consistent work environment.

Defaults also come with reliability. macOS defaults are thoroughly tested and vetted by Apple, ensuring stability and reducing the likelihood of crashes or compatibility issues. This reliability means fewer interruptions and more time dedicated to productive work.

Finally, simplicity should not be underestimated. A simpler setup means fewer points of failure and easier troubleshooting if issues arise, making macOS a pragmatic choice for developers seeking efficiency and stability.

What customizations are still necessary on macOS?

• Rectangle: Quickly manage window sizes and positions using customizable hotkeys. This tool brings efficient window management similar to what Linux users love.

• Karabiner Elements: Essential for customizing keyboard layouts. Remap keys and create complex modifications. For instance, remap your Caps Lock key to perform more useful functions like additional control keys.

• Homebrew: Install and manage packages efficiently. Homebrew brings the same ease of package management found in Linux distributions, allowing the installation of essential developer tools.

• iTerm2: Enhance the default terminal experience with features like split panes, extensive customization options, and better search functionality. iTerm2 is crucial for a more productive command line interface.

• BetterTouchTool: Customize and enhance the usability of trackpad and mouse gestures. It can also be used to assign custom shortcuts and actions, boosting overall productivity.

• VS Code: Although macOS comes with a decent text editor, Visual Studio Code offers numerous extensions and integrations tailored for various development needs, making it indispensable.

• Alfred: Replace the default macOS spotlight with Alfred for a more powerful and flexible search experience. It provides quick access to files, web searches, and custom workflows.

Implementing these tools ensures a balance between the seamless experience of macOS defaults and the productivity enhancements necessary for a developer's workflow.

Is there still room for Linux in your workflow?

Yes, Linux remains an essential part of the workflow. Although macOS is the primary operating system, Linux is indispensable for certain tasks.

• Server Hosting: Many servers still run on Linux. It's stable, secure, and efficient for handling backend operations.

• Specific Development Environments: Some development tasks are better suited to Linux. This includes containerization using Docker and running headless setups for automation scripts.

• Experimentation: Linux is great for trying out new software and configurations. It offers an open and flexible environment for testing ideas without impacting the primary macOS setup.

Despite the transition to macOS, Linux continues to be a valuable tool for these specific use cases.