How I'm switching to Quickshell.

Added: 2026-06-03

[00:00:00]I have been using Hyperland for almost a year now and when I first started I used Var like basically everyone else does but around a week ago I started switching to quick shell after seeing a bunch of really cool rides on R/ Unix porn. I haven't fully gone all out with quick shell yet though. Right now I only built a bar. The one you see right here, I built it using quick shell. And honestly, compared to Vivar, it was way hard. Even though I have been coding for around 2 and 1/2 year now, I know Python, JavaScript, TypeScript, and C++, Quickshell still felt difficult at first. Let me show you the code. All of this code you see right here is just to build this bar. And compared to Wear, it is a lot more work. And uh you have to define things like processes, layout and everything. You can use cell command to get the data and then you can parse it and then display it like that like I I'm doing it right here. So it is complicated but you can learn it definitely. Now some of you wondering if I know TypeScript and JavaScript why not just use AG as I'm just sick of Node modules. I don't want to work with JavaScript, TypeScript anymore because it just sucks. I don't want to write code engine in those language anymore. I just remember my React Native days with those languages.

[00:01:16]I don't want to deal with it deal with node modules anymore. And QT and QML system that QuickShell uses honestly feel way more cleaner to me. After building this bar, I start feeling way more confident. I watched some video read the docs and yeah you have to read the docs if you want to if you want to build a cool rise that you can post on R select Unix pawn and Linux pore now I'm planning to build more stuff with it like notification music player system monitor dropown menus basically all those cool stuff that you see on quick shell rises and most of the quick shell setups but I'm building everything one step at a time instead of trying to do everything at once because otherwise it will feel overwhelming really fast I also realize something. I don't want to copy other people's configs because when you want to make changes to them, it gets hard because you don't know what piece of code who does what and where to make changes, where to exactly go to find that exact error you are getting.

[00:02:13]And I just don't like copy pasting. So that's why I decided to build myself.

[00:02:18]And when you build things by yourself, you understand what exactly a piece of code does, why decision were made, where things break and how actually fix them.

[00:02:27]So if you try if you want to try cook shell don't go all out immediately like I still use things like vbar I doesn't delete its config and var because I use it sometimes like want to see that what things I need to add to my quick shell configuration and I use rui soc and many more things that can be replaced use replaced by quick shell but I didn't replace them yet because I'm learning and I'm building one thing at a time not trying to build everything at once.

[00:02:57]I still don't fully understand QT and QML either. But being a developer definitely helps because I can understand code even if I don't fully know the language yet. But honestly, even if you never writed code before, I think you can still learn QML. If you already comfortable using Hyperland, there are tons of resources like YouTube video documentation, config example, you can use them. And when you don't understand a thing, you can just ask AI because we are living in a AI era right now. So why not just use it for good things instead of generating slop. But if you are completely new to Hyperland, I did say don't switch to QuickShell immediately because you should spend some times configuring Hyperland using different tools and decide whether you want to switch to QuickShell or not. So yeah, that's basically my experience switching to QuickShell and I will keep continuing it and making some more changes to it, building more stuff with QuickShell. And if you want to check out my configuration, I leave a link in the description of my GitHub repo. You can definitely check that out. And that's it.