aboutsummaryrefslogtreecommitdiff
path: root/build/linux-love/index.html
blob: 3f52e61c348f918856a11c4a4ccbd81ddfe1b83a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
<!doctype html>
<html lang="en">
<head>
	<meta charset="utf-8">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<link rel="icon" href="data:,">
	<title>The Linux Desktop is Hard to Love</title>
	<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
	<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
</head>

<nav>
	<a href="#menu">Menu &darr;</a>
</nav>

<main>
<h1 id="the-linux-desktop-is-hard-to-love">The Linux Desktop is Hard to Love</h1>

<p>2022-07-14</p>

<p>I want to love the &#8220;Linux Desktop&#8221;. I really do. But I&#8217;ve come to the realization that what I love is the <em>idea</em> of the Linux Desktop. The community. The security and core focus on open source. The customizable environments. Tweaking as much or as little of the operating system as I please!</p>

<p>I just can&#8217;t <em>stick with it</em>. I always end up back on macOS. And I&#8217;m starting to understand why.</p>

<h2 id="what-the-linux-desktop-gets-right">What the Linux Desktop Gets Right</h2>

<p>To be fair, there is an incredible amount of things that the Linux desktop does really well:</p>

<ul>
<li>Complete user control</li>
<li>Ability to drastically change the desktop UI

<ul>
<li>Gnome, KDE, XFCE, etc.</li>
</ul></li>
<li>Overall good and welcoming communities</li>
<li>Extensive documentation for almost everything</li>
</ul>

<p>These things make Linux a solid experience overall - but not a <em>great</em> one&#8230;</p>

<h2 id="what-the-linux-desktop-gets-wrong">What the Linux Desktop Gets Wrong</h2>

<p>If I had to summarize in a word what Linux lacks compared to macOS it would be: <em>cohesion</em>.</p>

<p>Apple&#8217;s macOS keeps a solid consistency throughout its entire design. Everything looks and feels like it is part of the same system. Which is what a fully-fledged OS <em>should</em> feel like. The argument can be made that macOS suffers some fragmentation with things like <code>homebrew</code>, applications directly from developers vs. applications via the Mac App Store.</p>

<p>While this is true, I believe Linux desktops suffer far worse in terms of fragmented systems. Users building applications from source, <code>snap</code> packages, <code>flathub</code> packages, custom package managers shipped with separate distros, etc. And with this fragmentation comes the constant debates and discussions around which to use and which to avoid.</p>

<p>This can become overwhelming for average computer users. This is something we tend to forget in our &#8220;tech hubs&#8221;. Most users want to boot up their machine and get to work. Linux can absolutely do this, but if a user hits a minor snag, then I guarantee they will have more difficulty fixing it compared to an issue found in macOS.</p>

<h2 id="user-experience">User Experience</h2>

<p>Design is important. The user experience will make or break an operating system. This is another issue I&#8217;ve found with many Linux desktops.</p>

<p>Let&#8217;s take Bluetooth for example. It works flawlessly in macOS. I have never had a single device bug-out or refuse to connect. Devices connect almost immediately when pairing. The UI is intuitive and gives the user clear feedback to what the system is doing while pairing, disconnecting, and so on.</p>

<p>Now, compare this to an average Linux DE experience - not so seamless. The fact that some distros require you to hop into a terminal in order to properly configure Bluetooth is pretty terrible. Sure, most have GUIs setup similar to that of macOS, but I find myself time and time again needing to pop open that trusty ol&#8217; Terminal. This is fine for someone like myself, but for the average computer user? No way.</p>

<p>Looking for another example? Printers. Yes, printers are terrible machines created in the depths of Hell itself, but they are a necessary evil. And again, macOS handles &#8220;plug-and-play&#8221; printer functionality like a champ. Linux on the other hand is a mixed bag. I&#8217;ve had some luck with specific Linux distros working with printers in this &#8220;plug-and-play&#8221; fashion, while others become a battle of attrition[^1]. Let&#8217;s not even begin to talk about wireless <em>only</em> printers and setting up their proper drivers on Linux.</p>

<h2 id="quality-hardware">Quality Hardware</h2>

<p>Another advantage macOS has over most other Linux desktops is tailored hardware. Apple produces the hardware created to run their own operating system, meaning it was specifically built for that task. Linux desktops are designed to run on almost any[^2] piece of hardware. Though this is fantastic in terms of technological sustainability (avoids dumping old devices when they lose &#8220;support&#8221;) it ends up causing more support issues. Needing to support such a wide range of chip sets and drivers spreads the focus on a streamlined UX a little more thin. It becomes difficult to perfect a cohesive experience user-to-user when some many variables can be different. I should note that some distros[^3] are making fantastic strides in this area but are still far from ideal.</p>

<h2 id="i-still-use-linux">I Still Use Linux</h2>

<p>I might have attacked the overall Linux desktop experience in favor of macOS a little harshly in this post, but it&#8217;s a simple reflection of a individual who has used both extensively. I still work with multiple Linux machines daily. I still <em>like</em> using Linux.</p>

<p>I just don&#8217;t <em>love</em> it.</p>

<h2 id="refs">Refs</h2>

<ol>
<li>People swear by CUPS working well on Linux, but this has caused issues for me in the past as well. Unsure why macOS handles it fine&#8230;</li>
<li>Depending on the desired distro, resources required, etc.</li>
<li>A couple that come to mind are Zorin OS and elementary OS</li>
</ol>
<footer role="contentinfo">
    <h2>Menu Navigation</h2>
    <ul id="menu">
        <li><a href="/">Home</a></li>
        <li><a href="/projects">Projects</a></li>
        <li><a href="/uses">Uses</a></li>
        <li><a href="/wiki">Wiki</a></li>
        <li><a href="/resume">Resume</a></li>
        <li><a href="/colophon">Colophon</a></li>
        <li><a href="/now">Now</a></li>
        <li><a href="/donate">Donate</a></li>
        <li><a href="/atom.xml">RSS</a></li>
        <li><a href="#top">&uarr; Top of the page</a></li>
    </ul>
    <small>
        Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br>
        Maintained with ♥ for the web. <br>
        Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> &amp; <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br>
        The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>.
    </small>
</footer>