<?xml version="1.0" encoding="UTF-8"?>
<rss  xmlns:atom="http://www.w3.org/2005/Atom" 
      xmlns:media="http://search.yahoo.com/mrss/" 
      xmlns:content="http://purl.org/rss/1.0/modules/content/" 
      xmlns:dc="http://purl.org/dc/elements/1.1/" 
      version="2.0">
<channel>
<title>digenoma</title>
<link>https://adigenova.github.io/alexcbblog/en/blog.html</link>
<atom:link href="https://adigenova.github.io/alexcbblog/en/blog.xml" rel="self" type="application/rss+xml"/>
<description>Computational biology in the wild.</description>
<generator>quarto-1.10.18</generator>
<lastBuildDate>Sun, 30 Aug 2026 00:00:00 GMT</lastBuildDate>
<item>
  <title>Back to Linux after 16 years: from macOS to Omarchy</title>
  <dc:creator>adigenova </dc:creator>
  <link>https://adigenova.github.io/alexcbblog/en/posts/2026-08-30-macos-to-omarchy/</link>
  <description><![CDATA[ 





<p>For a long time, I thought my story with Linux as a desktop operating system was over.</p>
<p>I started using Linux around 2003, when it was perfectly normal to install something on a computer and spend the next several hours figuring out why the sound, graphics card, Wi-Fi—or, on particularly lucky days, all of them—did not work.</p>
<p>I used it as my main system until roughly 2010. I tried several distributions, configured desktops, broke configurations, fixed them, and learned much of what I know about computers precisely because Linux forced me to understand what was happening under the hood.</p>
<p>I even went through an <strong><a href="https://www.enlightenment.org/">Enlightenment</a></strong> phase, trying to build the minimalist, beautiful, futuristic Linux desktop I imagined ought to exist.</p>
<p>It was beautiful.</p>
<p>Sometimes.</p>
<p>When it worked.</p>
<p>Then macOS arrived, and for about 16 years I practically stopped using Linux as a desktop.</p>
<p>But Linux never really disappeared from my life.</p>
<p>It simply moved to the cluster.</p>
<section id="linux-never-left" class="level2">
<h2 class="anchored" data-anchor-id="linux-never-left">Linux never left</h2>
<p>While my personal computer became a Mac, much of my scientific work continued to happen on Linux.</p>
<p>Kütral runs on CentOS. Leftraru runs on Red Hat. Nearly every server, cluster, and machine where I perform important bioinformatics analyses runs some variant of Linux.</p>
<p>My computational life settled into a natural division:</p>
<p><strong>macOS on the laptop, Linux on the cluster.</strong></p>
<p>That combination worked extraordinarily well for many years. Meanwhile, something else quietly changed: <strong>my data stopped truly living on my computer</strong>.</p>
<p>Code moved to <a href="https://github.com/">GitHub</a>. Documents moved to Google Drive. Music moved to Apple Music. Scientific repositories live on servers, large datasets on clusters, and important analyses run remotely. Even much of our software has become a web service.</p>
<p>Without noticing, my computer stopped being the place where my things lived. It became primarily <strong>an interface for reaching them</strong>.</p>
<p>That changes the question of which operating system I need.</p>
</section>
<section id="something-began-to-feel-strange-in-macos" class="level2">
<h2 class="anchored" data-anchor-id="something-began-to-feel-strange-in-macos">Something began to feel strange in macOS</h2>
<p>There was no particular day when I declared:</p>
<blockquote class="blockquote">
<p>That’s it. I’m leaving macOS.</p>
</blockquote>
<p>It was much more gradual. My M1 Pro MacBook Pro remains an excellent computer. In fact, that becomes a problem later in this story.</p>
<p>But macOS had begun to feel less comfortable for how I work. Part of it was small operational annoyances: Google Chrome consuming absurd amounts of memory, frozen screens, and the system occasionally entering a state that makes you think:</p>
<blockquote class="blockquote">
<p>This should not be happening on a computer this expensive.</p>
</blockquote>
<p>But something else was more interesting.</p>
</section>
<section id="the-chatbots-arrived" class="level2">
<h2 class="anchored" data-anchor-id="the-chatbots-arrived">The chatbots arrived</h2>
<p>An important part of my workflow changed over the last few years: <a href="https://chatgpt.com/">ChatGPT</a>, <a href="https://openai.com/codex/">Codex</a>, and LLMs in general appeared.</p>
<p>They quickly went from curiosities to tools I use frequently: for programming, exploring ideas, reviewing code, understanding errors, discussing analyses, writing, finding alternatives, and answering the small questions that once meant twenty minutes among <a href="https://stackoverflow.com/">Stack Overflow</a>, documentation, and an abandoned GitHub issue from 2017.</p>
<p>The traditional macOS application model began to feel less natural for this way of working. My work increasingly revolved around:</p>
<p><strong>terminal + browser + editor + chatbot + cluster.</strong></p>
<p>macOS started to feel like an extra layer between those things. Nothing dramatic; it simply stopped feeling entirely natural.</p>
<p>Then a dangerous idea appeared:</p>
<blockquote class="blockquote">
<p>What if I go back to Linux?</p>
</blockquote>
</section>
<section id="practicing-what-i-teach" class="level2">
<h2 class="anchored" data-anchor-id="practicing-what-i-teach">Practicing what I teach</h2>
<p>There was another reason that particularly bothered me as a computing professor. In several courses I teach Linux, the terminal, SSH, clusters, advanced programming, and scientific tools.</p>
<p>During a recent class, I had a slightly uncomfortable realization: I was teaching students that Linux was fundamental to computational science…</p>
<p>…from a Mac.</p>
<p>There is no technical contradiction, of course, but it began to feel inconsistent. A Mac is also expensive. If I teach tools that should let a student build an excellent working environment with free software and ordinary hardware, it made sense to try living in that ecosystem myself.</p>
<p>Something like <strong>practicing what I teach</strong>.</p>
<p>So I did what we all do when we want to make a perfectly rational technology decision: I looked for what was <em>hot</em>, checked GitHub trends, and found <strong><a href="https://omarchy.org/">Omarchy</a></strong>.</p>
</section>
<section id="what-the-hell-is-omarchy" class="level2">
<h2 class="anchored" data-anchor-id="what-the-hell-is-omarchy">What the hell is Omarchy?</h2>
<p>Omarchy is a Linux environment based on <a href="https://archlinux.org/">Arch Linux</a> and <a href="https://wiki.hypr.land/">Hyprland</a>, with a clear philosophy: much of the system is keyboard-driven, applications automatically use the available space, and the desktop stays visually clean.</p>
<p>My first reaction was:</p>
<blockquote class="blockquote">
<p>This looks suspiciously beautiful for Linux.</p>
</blockquote>
<p>For years, I had tacitly accepted a universal law:</p>
<p><strong>Linux can be powerful or beautiful, but attempting both requires sacrificing several weekends.</strong></p>
<p>Omarchy seemed determined to break that rule. Apple Silicon support was also available thanks to the enormous effort behind <a href="https://asahilinux.org/">Asahi Linux</a>.</p>
<p>I had a MacBook, free disk space, and curiosity. Clearly, I had to do something irresponsible =).</p>
</section>
<section id="the-moment-we-start-sweating-again" class="level2">
<h2 class="anchored" data-anchor-id="the-moment-we-start-sweating-again">The moment we start sweating again…</h2>
<p>Installation was straightforward, except for one small detail: resizing the macOS partition.</p>
<p>Watching the resize process immediately brought back my university years—especially the occasions when, while experimenting with Linux partitions, I erased operating systems I had absolutely not intended to erase.</p>
<p>Some knowledge never leaves you. Neither does trauma.</p>
<p>The difference today is that almost everything important is in the cloud. My code is on GitHub, documents are synchronized, scientific data is on servers, and photos are backed up. The real risk was far smaller than it was twenty years ago.</p>
<p>Still, watching a tool modify the partitions on the disk containing your digital life produces a healthy amount of adrenaline.</p>
<p>I finished the installation, rebooted, selected Linux in the bootloader, and it worked.</p>
<p>That first boot produced an interesting mixture of satisfaction and:</p>
<blockquote class="blockquote">
<p>Well… apparently I didn’t erase macOS.</p>
</blockquote>
<p>Success.</p>
</section>
<section id="for-the-first-time-i-found-linux-genuinely-beautiful" class="level2">
<h2 class="anchored" data-anchor-id="for-the-first-time-i-found-linux-genuinely-beautiful">For the first time, I found Linux genuinely beautiful</h2>
<p>This was probably my first major surprise. Omarchy is <strong>beautiful</strong>.</p>
<p>Not beautiful “considering it is Linux.” Beautiful. Period.</p>
<p>The typography. The spacing. The terminals. The animations. The visual consistency. Dark mode. The way windows appear. Everything has a coherent aesthetic.</p>
<p>For someone who had tried to build something similar with Enlightenment years earlier, it was impressive that all of this was simply there.</p>
<p>But the most interesting part was not its appearance. It was the window system.</p>
</section>
<section id="where-did-hyprland-come-from" class="level2">
<h2 class="anchored" data-anchor-id="where-did-hyprland-come-from">Where did Hyprland come from?</h2>
<p>At first, you have to forget certain habits. On macOS, I had years of muscle memory: <code>Command + Tab</code>, Mission Control, floating windows stacked on top of one another, dragging, resizing, and hunting for a particular application.</p>
<p>Omarchy uses Hyprland and a tiled-window model.</p>
<blockquote class="blockquote">
<p>In the 2000s, I tried to build this desktop with Enlightenment; twenty years later, I discovered that Hyprland was what I had been looking for.</p>
</blockquote>
<p>Open something and the system finds a place for it. Open something else and the space reorganizes. Change workspaces, move windows, and close applications from the keyboard. Almost everything happens without touching the mouse.</p>
<p>Unexpectedly, <strong>this feels much more natural to me than a traditional desktop</strong>.</p>
<p>For years, I stopped considering Linux a real desktop alternative. I still used it daily on servers and clusters, but in my mind it remained frozen as the system I had left when I moved to macOS.</p>
<p>Hyprland showed me how much Linux had changed while I was, paradoxically, still using it every day—just on the other side of an SSH connection.</p>
<p>Almost immediately, I had something like:</p>
<pre class="text"><code>Workspace 1 → code
Workspace 2 → terminals and cluster
Workspace 3 → browser and papers
Workspace 4 → ChatGPT
Workspace 5 → everything else</code></pre>
<p>and I was jumping among them almost without thinking. It is fast. Very fast. The computer stops feeling like a collection of windows and starts feeling like a set of workspaces.</p>
<p>Perhaps this is a newcomer’s enthusiasm, but it is one of the things that has impressed me most.</p>
</section>
<section id="the-small-problem-with-super-w" class="level2">
<h2 class="anchored" data-anchor-id="the-small-problem-with-super-w">The small problem with SUPER + W</h2>
<p>Changing 16 years of muscle memory has consequences.</p>
<p>On macOS, <code>Command + W</code> closes the active tab or window. In Omarchy, <code>SUPER + W</code> closes the application.</p>
<p>For the first few days, whenever I wanted to close a Chromium tab, my fingers repeated the gesture learned over years on macOS—and closed the entire application.</p>
<p>Not the tab. The application.</p>
<p>I had also misunderstood another shortcut: I thought <code>SUPER + T</code> would open a terminal. In Omarchy, it actually toggles the window state.</p>
<p>So the problem was not filling the desktop with new terminals. It was more efficient than that: I abruptly closed whichever application I was using.</p>
<p>After 16 years, muscle memory needs time to accept that <code>Command</code> and <code>SUPER</code> do not speak precisely the same language.</p>
<p>The brain is still migrating.</p>
</section>
<section id="the-hardware-simply-works" class="level2">
<h2 class="anchored" data-anchor-id="the-hardware-simply-works">The hardware… simply works</h2>
<p>This may contrast most sharply with my memories of Linux. Twenty years ago, installing Linux often meant opening diplomatic negotiations with the hardware: graphics card, drivers, Wi-Fi, audio, suspend, brightness. Something always refused to cooperate, and GPUs deserved their own category of suffering.</p>
<p>That is why discovering how much <strong><em>everything has changed</em></strong> surprised me.</p>
<p>Omarchy recognized practically all my hardware, including the GPU. I quickly began testing <strong>local LLMs</strong> with graphics acceleration.</p>
<p>A language model running locally on a Mac GPU—in Arch Linux—and working would have sounded like science fiction during my first Linux era.</p>
<p>There were small things to configure. Keyboard illumination initially misbehaved, brightness keys needed configuration, and the time zone briefly decided Chile was elsewhere on the planet. But these problems were small and, more importantly, <strong>understandable</strong>.</p>
<p>Not weeks spent compiling a driver found on a Russian forum.</p>
<p>Linux has changed enormously.</p>
</section>
<section id="rebuilding-my-computer-was-surprisingly-easy" class="level2">
<h2 class="anchored" data-anchor-id="rebuilding-my-computer-was-surprisingly-easy">Rebuilding my computer was surprisingly easy</h2>
<p>Then came a revealing experiment: what do I really need to reconstruct my digital life?</p>
<p>GitHub. Configured.</p>
<p>Google Drive. Accessible.</p>
<p>Apple Music. Opened in Chromium. It worked immediately.</p>
<p>Omarchy can install web apps as ordinary applications, so Apple Music became a standalone app. The same happened with ChatGPT and YouTube.</p>
<p>Python and <code>uv</code>. Done.</p>
<p>Git. GitHub CLI. SSH. Nextflow. LaTeX. Quarto. Access to the clusters.</p>
<p>In very little time, I had nearly my entire working environment again. This would have been far more traumatic 16 years ago. The cloud completely changed what reinstalling a computer means.</p>
</section>
<section id="linux-configuring-linux-with-help-from-ai" class="level2">
<h2 class="anchored" data-anchor-id="linux-configuring-linux-with-help-from-ai">Linux configuring Linux with help from AI</h2>
<p>One particularly entertaining part of this experience is how I configured Omarchy.</p>
<p>Install something. Encounter a problem. Ask ChatGPT. Change a setting. It works. Move on.</p>
<p>At some point, I realized I was using ChatGPT inside Omarchy to learn how to configure Omarchy while Omarchy ran local AI tools.</p>
<p>It is a kind of computational bootstrap for 2026—and a demonstration of why I wanted this change.</p>
<p><strong>Linux + terminal + LLM</strong> feels extremely natural.</p>
<p>A chatbot explains a configuration. I open the file, modify it, test it, show the error, and correct it. Everything happens in a very short loop.</p>
<p>LLMs also reduce one of Linux’s historical barriers: the bits of specific knowledge needed to solve hundreds of different problems.</p>
<p>Before: Google. Stack Overflow. <a href="https://wiki.archlinux.org/">ArchWiki</a>. Three contradictory posts—one written in 2014, another saying “solved” without explaining how.</p>
<p>Now I can often begin simply by asking. The model can be wrong, of course, but as an interface for exploring the system it is extraordinarily useful.</p>
<p>Chatbots make Linux <strong>far more accessible than it was during my first era using it</strong>.</p>
</section>
<section id="my-daughters-have-another-explanation" class="level2">
<h2 class="anchored" data-anchor-id="my-daughters-have-another-explanation">My daughters have another explanation</h2>
<p>My daughters saw the new desktop: terminals, keyboard-driven windows, text everywhere, dark background. They quickly delivered their diagnosis:</p>
<blockquote class="blockquote">
<p>Dad, it looks like a hacker’s computer.</p>
</blockquote>
<p>I did not argue. After twenty years working in bioinformatics and genomics, I had apparently finally made my computer match the cinematic portrayal of my profession.</p>
</section>
<section id="so-am-i-deleting-macos" class="level2">
<h2 class="anchored" data-anchor-id="so-am-i-deleting-macos">So, am I deleting macOS?</h2>
<p>No.&nbsp;Not yet.</p>
<p>This is probably the least romantic but most reasonable part of the story. There is still testing to do: external displays, peripherals, projectors, and the small hardware details that only appear over time. The audio sometimes crackles and does not feel particularly high quality.</p>
<p>I want to know how it behaves after weeks and months, not only during the honeymoon of the first few days.</p>
<p>There is another important problem: <strong>I still cannot find a laptop beautiful enough to replace my MacBook.</strong></p>
<p>Apple makes absurdly good hardware. My problem was never the computer.</p>
<p>For now, I have both. macOS remains there. So does Omarchy. I can boot either one. The difference is that during these first few days, I have not felt much desire to return to macOS.</p>
</section>
<section id="after-fedora-debian-ubuntu-enlightenment-and-macos" class="level2">
<h2 class="anchored" data-anchor-id="after-fedora-debian-ubuntu-enlightenment-and-macos">After Fedora, Debian, Ubuntu, Enlightenment, and macOS…</h2>
<p>I have tried enough systems not to declare eternal love for a distribution after 48 hours: Fedora, Debian, Ubuntu, different desktops, Enlightenment, and macOS for more than a decade.</p>
<p>On Linux desktops, I always found some combination of functionality, aesthetics, and usability that did not quite convince me. Omarchy is the first time in a long while that I feel something different.</p>
<p>Arch provides an enormous ecosystem. Hardware detection is incomparably better than in the Linux I remember. Hyprland completely changed my perception of how a desktop should work. Integration with modern tools is excellent.</p>
<p>And, surprisingly importantly: <strong>it is beautiful.</strong> Very beautiful.</p>
<p>For now, the combination of power, simplicity, usability, and aesthetics has me quite excited. We will see how long that lasts.</p>
<blockquote class="blockquote">
<p>A beautiful system is a motivating system, and motivation brings ideas to life, like this blog!</p>
</blockquote>
</section>
<section id="returning-but-to-a-different-linux" class="level2">
<h2 class="anchored" data-anchor-id="returning-but-to-a-different-linux">Returning, but to a different Linux</h2>
<p>Strangely, I do not feel that I have returned to the Linux I left in 2010. That system no longer exists.</p>
<p>Hardware changed. The cloud changed where our data lives. GitHub changed how we manage code. Clusters changed how we do scientific computing. LLMs are changing how we program and interact with computers. Linux changed too.</p>
<p>Perhaps that is why returning after so many years feels surprisingly natural. My personal computer now speaks almost the same language as the clusters where I work every day. The keyboard has become the primary interface again. The system gets out of the way.</p>
<p>And when I need to understand something, I probably have the best Linux documentation that has ever existed—plus a chatbot willing to accompany me while I inevitably break something.</p>
</section>
<section id="and-that-is-what-this-blog-will-be-about" class="level2">
<h2 class="anchored" data-anchor-id="and-that-is-what-this-blog-will-be-about">And that is what this blog will be about</h2>
<p>This migration also motivated me to do something I had considered for a long time: write about the small adventures surrounding my work.</p>
<p>Not only finished papers, but also the things normally left out: an analysis idea, an algorithm, a strange genomics problem, a genome assembly that refuses to cooperate, a cluster, an interesting paper, an experiment with an LLM, a Linux configuration, a good figure, or an idea that seemed brilliant at 11 p.m. and considerably less brilliant the next morning.</p>
<p>Much of computational biology happens precisely there—in that mixture of science, programming, computers, experimentation, and curiosity.</p>
<p>So this blog appropriately begins with a migration, a change, an action.</p>
<p>After roughly 16 years using macOS as my main desktop, I returned to Linux. This time on an M1 Pro MacBook. With Omarchy.</p>
<p>The window system fascinates me. The GPU works. Local LLMs work. Apple Music works. I did not accidentally erase the disk.</p>
<p>And my daughters think I am now a hacker.</p>
<p>For the moment, I consider the experiment a success.</p>
<div class="quarto-figure quarto-figure-center">
<figure class="figure">
<p><img src="https://adigenova.github.io/alexcbblog/en/posts/2026-08-30-macos-to-omarchy/figures/omarchy-desktop.png" class="img-fluid figure-img" style="width:100.0%" alt="Omarchy desktop on a MacBook with the digenoma site, Apple Music, and several tiled terminals"></p>
<figcaption>My Omarchy desktop: the digenoma site, Apple Music, terminals, and monitoring tools arranged with Hyprland.</figcaption>
</figure>
</div>


</section>

 ]]></description>
  <category>Linux</category>
  <category>Omarchy</category>
  <category>Computational Biology</category>
  <guid>https://adigenova.github.io/alexcbblog/en/posts/2026-08-30-macos-to-omarchy/</guid>
  <pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate>
</item>
</channel>
</rss>
