8/7/2023 0 Comments Cmus status polybar![]() That’s not only XMonad but also Polybar and Picom complementing it, a status bar and a compositor, respectively. This is what it looks like at the moment on my machine (it’s always evolving). There are many tutorials, blog posts, videos and documentation on the Internet about it so I’m only going to focus on getting XMonad properly set up in NixOS. XMonad is a dynamically tiling X11 window manager that is written and configured in Haskell. NOTE: If you are already familiar with all of this and are only interested in the configuration files, you can find them on my Github. ![]() How could I ever write imperative code again? The good news is that this incident has pushed me into giving XMonad a serious try, and oh boy, there’s no way back! It’s like that day I discovered functional programming. My mother still uses Gnome 3 with Ubuntu, FWIW :) I know writing solid software is hard and memory leaks are one of the toughest problems to solve in Software Engineering so I only want to thank Gnome for all the good years and wish only the best. I have screenshots of the memory consumption but I decided to leave them out of this post since it is not about bashing Gnome. Although it has been announced as allegedly solved, I have been experiencing a similar issue in Gnome 3.36 on NixOS.Īfter a fresh start, it consumed ~1.2% of my 32GB (about 390MB) but right after 24 hours (only one day of uptime!) I found out it was consuming ~50% (about 16GB!), which is unacceptable. However, the main reason is that Gnome leaks memory, unfortunately, and it seems to be an issue that’s been around forever. One of the reasons is that I’ve been wanting to try a lightweight window manager for a while. I’ve been a Gnome user for a long time and I have never cared about using a Window Manager ever before but I recently switched to using XMonad full-time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |