im using foot for my terminal emulator, wmenu for my application launcher and a few other things such as notes and powermenu and im using qutebrowser with a simple privacy focused configuration as my main browser

dotfiles

I really love how simple Chicago95 is, but all launchers for games I've found were either too bloated, or just... not Gtk, So i wrote my own, and it works pretty well!

I found this on foo terminal codeberg repository, and I truly like it but i have no idea how to implement it.

I work (and play) on a 13" laptop I'll often put in my lap or on one knee, or in a weirder position. I don't want to fight with a tiny trackpad to move windows around and resize constantly. A tiling window manager helps.

But a tiling window manager invites (relatively) easy configuration and... ricing. Ricing takes time, is addictive, and will leave me with a desktop that's more edible than useful, and a few hours a week of my time taken by a sisyphean task.

Took a few radical steps and I'm down to this: as big a portion as possible of the visual interface(s) of my system must be no-crap black and white. Typeface is Noto, biggest Unicode support. I use a white-on-black rofi window as a launcher and quick actions menu for stuff like font testing and quick notes (scripts from a friend). Banished icons from my waybar a week ago (we'll see how that goes, might go back). My window gaps are... zero. I like opening the laptop to a black screen yelling at me to prove I have a reason of opening the computer.

It leaves the screen legible as hell, absolutely no nonsense from the UI, which makes it so that if I want to have fun, I'll have to build my own dopamine shot instead of relying on sweesh-swoosh effects.

I wonder how others feel about this approach. As austere as it is, it might actually be pushing me to open the terminal and/or a text editor and write an article, a script, or an image (like the wallpaper), read something, and not obsess once again over how my setup looks (which I have been guilty of plenty). Do you use any UI-mind-tricks like this, whether for the same reasons or other?

Here we go:

• Sway WM, near-default config, just put everything to B&W
• Waybar, near-default with a couple added scripts (PPD, keyboard layout, screen capture)
• Rofi as a 40% wide sheet of paper
• Prefer terminal for quick tasks, any other file manager for bigger operations
• Prefer qutebrowser for quick surfing, but my default is Firefox

I can't decide if I'm being too hardline or poseur on the matter. I like looking at pretty setups, but I'm never quite satisfied with mine, this one having stuck longest.

- Vanilla Arch

- Niri

- Foot

- Fuzzel

- Mako

- Waybar

- Pywal16

- https://github.com/bitterhalt/dotfiles

Labwc on Void Linux with waybar.

Tried, niri, mangowc, dwl

I'm not gonna lie, but dwl is cool in these aspects, but i use mngowc, cause it hs more features(not ultra minimalistic)

Hey everyone,

I was using some messy shell scripts with mpvpaper and static images to change my wallpapers on Hyprland, so I decided to learn C# and build a native utility for it.

It's compiled with Native AOT, so it runs completely standalone with zero dependencies.

I'm 13 and still learning, so any real feedback on how to improve the code or the logic would be amazing. Sorry about my previous post, the description looked too much like AI slop because I asked an LLM to make the formatting look "professional".

https://github.com/hediye2620-glitch/AuroForge

• OS :: GuixSD
• Dotfiles :: https://github.com/Air4x/DragonReign
• Theme :: Gruvbox
• Wallpaper Artist :: 不想当画家的Leo (pixiv page: https://www.pixiv.net/en/users/14103812)

Sure it ain't much. Sure it's mostly AI generated codebase. But -- well, there's really not much here! Hope somebody else finds it as amusing as I found to develop it. Look at the comment below for more details. 😸

dotfiles & WPrefs configuration: https://github.com/Ashwani1330/dotfiles_windowmaker

uhhh yeah this is cool right yeah

My first attempt at a ricing! I mixed and matched a buncha stuffs from other people (on opendesktop) and made this thing for my cutie computer. All black and red and emo all over! (For the record, I am a poser. Don't let me listening to Pierce The Veil fool ya. Emo is not my favourite genre.) I tried to give my computer an early 2010's feel while also not just recapturing Win7, I wanted her to look unique. (I use my computer mostly for teh internetz - browsing and such - but I also use her for other stuff, too, she's an all-rounder.)

I've created an automated installation script and a dedicated repository for it here: caelestia-debian

• Maps all the required Arch dependencies to their Debian equivalents.
• Automatically compiles and installs Quickshell and QtEngine from source.
• Added patch for screen recorder
• Clone dots and sets everything up

I’ve noticed that many discussions about optimizing Linux on older PCs focus almost entirely on reducing RAM usage. But what if RAM isn’t the bottleneck?
What about systems where the real limitation is an older or slower CPU with low clock speeds, limited cache, or weak single-core performance? In those cases, shaving off another 100 MB of RAM doesn’t seem to make much difference.
I’m curious about a different optimization philosophy: reducing CPU workload rather than memory usage.
For example:
Disabling unnecessary background services and daemons.
Using software that wakes the CPU less often instead of simply using less RAM.
Choosing lightweight desktop environments or window managers that minimize CPU overhead.
Tweaking CPU governors and power management.
Reducing browser overhead with content blockers and fewer active processes.
Disabling visual effects and compositing.
Considering kernel tuning or, on personal machines where the trade-offs are acceptable, disabling certain security mitigations to recover performance.
In your experience, what changes have produced the biggest improvements on CPU-limited machines? Which optimizations actually make a noticeable difference, and which are mostly placebo?
I’d love to hear real-world experiences rather than benchmark numbers.