diff options
| author | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:22:21 -0400 |
|---|---|---|
| committer | Bradley Taunt <bt@btxx.org> | 2024-07-02 14:22:21 -0400 |
| commit | 3f6a9546ec13063d0d5bdf21d30a93d3e8aa6050 (patch) | |
| tree | 947985c4eda1bceb1910bc01739c32fd0baad181 /build/posts/suckless/index.html | |
| parent | 14074019d62d98885c4c764401a9e7e1fd129f79 (diff) | |
Diffstat (limited to 'build/posts/suckless/index.html')
| -rw-r--r-- | build/posts/suckless/index.html | 87 |
1 files changed, 0 insertions, 87 deletions
diff --git a/build/posts/suckless/index.html b/build/posts/suckless/index.html deleted file mode 100644 index 6291473..0000000 --- a/build/posts/suckless/index.html +++ /dev/null @@ -1,87 +0,0 @@ -<!doctype html> -<html lang="en"> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - <meta name="color-scheme" content="dark light"> - <link rel="icon" href="data:,"> - <title>I Want to Suckless and You Can Too</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;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}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 ↓</a> -</nav> - -<main> -<h1 id="i-want-to-suckless-and-you-can-too">I Want to Suckless and You Can Too</h1> -<p>2022-12-23</p> -<h2 id="the-desire-to-suckless">The Desire to Suckless</h2> -<p>While I have been happy with my <a href="/alpine">previous desktop setup</a> using Wayland on Alpine Linux, I just couldn’t shake the urge to fully embrace the <a href="https://suckless.org">suckless ecosystem</a>. Although, this meant ditching Wayland and returning to X11, which is apparently the new “cool thing to hate” in Linux land. At least, that’s what I’ve seen online lately.</p> -<p>But I’m getting ahead of myself…</p> -<h2 id="what-is-suckless">What is Suckless?</h2> -<p>I’m not going to spend too much time repeating what you can <a href="https://suckless.org/philosophy/">already read on the suckless.org website itself</a>, but in a nutshell:</p> -<blockquote> -<p>Software with a focus on simplicity, clarity, and frugality.</p> -</blockquote> -<p>The developers also pride themselves on catering to <em>advanced and experienced computer users</em>, which is actually a refreshing take in my opinion. There are enough pre-existing open source solutions for non-technical or average Linux users looking for a desktop system. Having an option that requires users to deep-dive into the code, compile the programs manually, and better understand the software they are running is a welcome addition.</p> -<p>This process of “owing your software” was one of the core concepts that initially grabbed my attention. I’ve always been mildly mediocre at reading and writing C (ie. enough to be dangerous), so the thought of jumping head first into a system that would require me to better learn that language was tempting[^1]. And that temptation was enough to give it a shot!</p> -<h2 id="lets-get-started">Let’s Get Started</h2> -<p>So I made my decision. I would (at the very least) <em>try</em> switching my daily driver over to a completely “suckless” system. But I was immediately faced with my first obstacle: <em>which distro should I use</em>?</p> -<p>I’m sure many would suggest Gentoo, since it follows the principles of suckless more than any other distribution on the market. But I don’t hate myself enough to go down that insane rabbit-hole. I’m hardly advanced enough to take on such a steep challenge, not to mention my plan was to build out a “setup script” so others could roll their own suckless build. Something like that looked daunting under Gentoo. Maybe in the future…</p> -<p>So what’s left? Void? Arch? Something fresh, like Metis? I really didn’t know the “best” choice. Maybe there were just <em>too many</em> options? </p> -<p>Luckily, I did know of a distro that was my go-to for most projects…</p> -<h2 id="trying-alpine">Trying Alpine</h2> -<p>Alpine Linux is one of the best distributions available. If you disagree, you clearly haven’t achieved galaxy-brain levels of intelligence and I feel sorry for you[^2].</p> -<p>Having just rolled my own <a href="https://git.sr.ht/~bt/alpine-linux-setup">installer script</a> for Wayland/Sway on Alpine, I figured why not piggyback off that existing project? Work smart not hard, right? So I started putting together an absolute <em>bare minimum</em> list of requirements I needed to get a proper desktop system running:</p> -<ul> -<li>working suspend/awake</li> -<li>working audio</li> -<li>working wifi/networking</li> -<li>reduced screen tearing (X11 gave me problems in the past with this)</li> -</ul> -<p>As you can see, I have very low expectations. But there were issues….</p> -<ol> -<li>I could not build my blog locally (built via Jekyll) since the <code>sass-embedded</code> dependencies has not been built against musl-libc.</li> -<li>VSCodium would require the extra “bloat” of the flatpak manager (not to mention the spotty support some applications have through flatpak/snap).</li> -<li>The distro/system <em>feels</em> like it was better designed with Wayland in mind. Too often I felt like I was losing an uphill battle wrestling against Alpine.</li> -</ol> -<h2 id="getting-sucked-into-the-void">Getting Sucked into the Void</h2> -<p>After mentioning my struggles on Mastodon, some <a href="https://fosstodon.org/@tdarb/109554576434981872">helpful friends suggested taking a look at Void</a>. I always knew of the project but never used it as a “daily driver”. Since this was overall one <em>large</em> experiment, I figured I’d give it a shot.</p> -<p>I’m glad I did. Void Linux is <em>pretty great</em>.</p> -<p>The installer seemed more complex than Alpine at first, but I found an excellent walkthrough <a href="https://linuxiac.com/void-linux-installation/">here</a> (which I was more beginner-friendly than the official docs). Once everything was set, it was time to run my suckless “installer”.</p> -<h2 id="introducing-void-suck">Introducing void-suck</h2> -<p>If you don’t care about the nitty-gritty details, feel free to just jump over to the <a href="https://git.sr.ht/~bt/void-suck">void-suck repo on scourehut</a> and read through the code yourself. There is nothing groundbreaking here. A huge inspiration came from <a href="https://github.com/mad-ara/void-rice">mad-ara’s “void-rice” project on Github</a> - so a big thanks to him for making that project in the first place!</p> -<p>You can find the basic instructions in the README of the project itself, but it pulls in just the required dependencies along with my own custom suckless tools. You can easily swap out these with your own or simply default to the standard ones provided by <a href="https://suckless.org">suckless.org</a>.</p> -<p>Everything <em>should</em> work out of the box, but in case it doesn’t please <a href="https://todo.sr.ht/~bt/void-suck">open a ticket</a> or <a href="https://lists.sr.ht/~bt/void-suck">submit a patch</a>. I’m certain I overlooked some items!</p> -<h2 id="closing-thoughts">Closing Thoughts</h2> -<p>We’ll see how things go. So far I’m enjoying my time with a much simpler desktop and the “forced” push towards getting better with C is an added bonus. I still love Alpine, but Void is slowly winning me over…</p> -<h2 id="refs">Refs</h2> -<ol> -<li>I find this to be the best way to learn new things. Reading technical books are helpful, but concepts never stick with me unless I am forced to implement them.</li> -<li>This is a joke. Alpine is certainly not for everyone. There are many more “fully featured” distros available and everyone should use what they enjoy! Try not to take my blog posts so seriously…</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">↑ Top of the page</a></li> - </ul> - <small> - Built with <a href="https://barf.btxx.org">barf</a>. <br> - Feeds: <a href="/atom.xml">Atom</a> & <a href="/rss.xml">RSS</a><br> - Maintained with ♥ for the web. <br> - Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> & <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>
\ No newline at end of file |