Hello, so im gonna preface with I know my thought process is odd but just hear me out. So in MY head i see my journey to daily driving linux in steps, first i used WSL on windows, then I moved on to running a linux server or 2 in my homelab, next I dual booted a linux distro like Ubuntu or Fedora, after that I fully utilized Fedora KDE which later I setup to run more like a tiling window manager, and now I am fully daily driving cachyOS with hyprland. SO all that to ask for some ideas of what is a logical next progression?
If your current setup meets your needs, why progress to a new OS or DE? If Cachy/Hyprland works for you, just try to learn to use it better or optimize it.
You seem to have enough experience to know how each distro/DE works for YOUR workflow.
If you want to tinker, add AI agents to â fixâ your problems or something. Maybe try that on a separate PC in case you do important work on your PC and donât want to have it busted from experimenting. Or run a server / homelab. Find a need you need to meet. De-google yourself, self-hostâŚ.
4 Likes
I found myself in a similar spot to you hanging taken a very similar progression. Iâm not aware of a logical next step, although Iâm sure thereâs plenty you can expand your knowledge and use of.
As Lurker pointed out, there may be more you can get out of your homelab server setup. Iâve found that thereâs a lot of rich value on that side of home computing.
Also, something absent from your progression that was in mine is changing the firmware on your phone. The custom OSes out there are really nice to prevent the tracking and spying thatâs baked into the retail software. Once I made the switch, the low-level anxiety that my spyware phone imposed upon me disappeared. Iâve been nothing but happy with the switch.
1 Like
Maybe have a vist to the good neighbors at OpenBSD?
After so much Linux a OS with some new things might be what you are looking for.
If you know Linux youâll manage fine on BSD.
1 Like
I like it, any self hosted services you personally like to de-google? (if you have gone down that path yourself)
Ive actually been thinking about switching back to android and away from iphone so i will definitely have to look into some fun phone OSes
At some point along the progression curve programming in the *nix environment becomes important.
You donât necessarily have to do it for the rest of your life, but knowing it makes you much more able to understand tradeoffs, discussions, how things work, why they might be slow, or why they might not work. I think all serious *nix users would get a good return on investment on working through K&R, which isnât too much work. APUE is worth a browse, see the shape of how to do various things. Of course networking is a big part of our lives, see Beejâs work.
You can read about things like sys calls, libc, how programs allocate memory (and how Linux overallocates), how seccomp, IPC or whatever work. But I find it doesnât stick very well for me unless I try to use it in code.
2 Likes
Another thought:
If you want to progress further down a path, it may pay to surround yourself when possible with those who are already further down the path.
1 Like
An alternative idea: Instead of âprogressingâ in switching between Linux distros/DEs, how about actually getting involved with a project as a volunteer? If you like CachyOS, find out what the opportunities to contribute there are. It could be anything from improving documentation to testing, to helping new users, etc.
4 Likes
FreeBSD?
You could start with GhostBSD, as that gives you FreeBSD with a GUI already installed, which makes it easier to explore. Find out what works for you, and what doesnât, then progress to âpureâ FreeBSD with probably your own idea of a DE.
And if that bores you after a while, thereâs OpenBSD and NetBSD, both more opinionated and less compatible than FreeBSD, but some people are happy with what these systems offer.
2 Likes
I donât think there is a natural next step. I am interested in security and privacy, so for me the next step was Qubes OS.
1 Like
What are you unsatisfied with? Why do you have to progress?
The progression is that of your own making. Just like Windows or any other thing, you would just use it and expand on the need as you see fit. For example, if you picked up video or photography, you would find the tools that best suit your need for that situation. Progression doesnât exist unless there is a need <<<
1 Like
In terms of Linux distros there isnât a next step, you can try freebsd and itâs variants if you want to but thatâs really it.
But in terms of your experience with Linux, you divide into tuning stuff to your liking and then automating it so that you never have to do it manually again.
For example, I am trying to make a bootstrap in python that setups up most of my linux desktop experience automatically so it installs all applications I use from what ever source I tell it to grab forum and does my all my alias,executable and configs for the terminal and etc.
1 Like
Maybe dink around with some smarthome stuff? While itâs not necessarily linux, thereâs a bunch of open source stuff running around that goes pretty deep. HomeAssistant, ESP32s, Thingino camera firmware, EchoMuse bootloaders, etc.
WHAT?! Omgarchy is THE next step in Linux⌠Try the future NOW, Now, nowâŚ.
(vibe coded for your pleasure, batteries not included)
To the topic though:
Youâve hit the point where your desktop works, itâs fast, and the novelty of configuring window borders, keybinds and themeing your fast / neo fetch has worn off. My answer? Stop consuming, start contributing.
The traditional path tells you to hop distros again, switch to BSD, or chase âartificial frictionâ just to feel like youâre learning / doing. But the real ânext levelâ of Linux isnât finding another OS to install, itâs crossing the line from a user to someone who actively puts something back into the ecosystem.
If youâre looking for what to do next, pick a lane and start building:
-
Triage and file real bug reports: Donât just work around a glitch. Reproduce it, pull the logs, isolate what broke, and hand the maintainer a clean, reproducible issue. Maintainers are starved for QUALITY reports from daily drivers that arenât Ai meat proxies (see, Iâm using it).
-
Package what you use: If thereâs an app, script, or utility you rely on that isnât cleanly packaged for Arch/Cachy, write the PKGBUILD. Maintain it. Take a tool someone else abandoned and bring it up to date. Although this is a bit of an issue right now, GOOD and HONEST maintainers are always needed.
-
Submit tiny pull requests: You donât need to rewrite a compositor. Fixing a broken link in a README, correcting an outdated build flag, or patching a simple path issue frees up upstream devs to focus on core work. One small PR every week or two builds serious momentum.
-
Build your own tool: If you find yourself writing a janky bash script to automate your setup, wrap it into a clean CLI or a basic GUI. Put it on GitHub, write actual documentation for it, and share it. Even a small 100-line utility that solves your specific headache will almost certainly help dozens of other people. (And donât let the angry neckbeard priesthood get in your way, they just need to be avoided)
-
Kill the gatekeeping: When the next wave of people show up asking basic questions about switching from Windows, be the person who helps them without the condescending âRTFMâ attitude. Helping a newcomer untangle their audio or fix their dual-boot does more for the platform than bragging about how your here and theyâre there. (we get it, youâre a Level 80 Dark Magic Linux Elf⌠nobody caresâŚ)
Linux exists because people got tired of the âwelded-shut hoodâ of proprietary tech and decided to build tools for each other. Youâve already got your daily driver dialed in - now go and fly my beautiful Linux butterfly, build something that makes the ecosystem a little better for the person coming up behind you. 
(Iâm feelinâ goofball today, Iâm not being condescending)
3 Likes