r/suckless

Just curious.

I'll start: none.

Lately I've been in a need for systray and tried to apply a patch to the newest dwm, unsuccessfully (the best I could do is apply the 6.3 patch to 6.3 dwm). Now I find myself thinking, that I don't actually want to put these nasty icons on my beautiful text-only bar. So are there any, like, pop-up systrays (that follow the suckless philosophy of course)? Or other solutions perhaps?

So in my efforts to have more suckless computing I decided to try a bunch of alternate high performance window managers.

This includes i3.
Old classic, tiling window manager. Somewhat enjoyable, but a bit annoying where the customization was concerned.

I spend a few days on it and while I enjoyed it it was more of a hassle.

Next I played around with some Hyprland.

It feels a lot sleeker than i3 and I like the defaults and tiling better.

Then I took IceWM for a spin.

Pretty minimal, comparatively easier customization of stuff like keybindings vs. i3 and a more orthodox desktop experience(Think windows 95)

Overall I enjoyed IceWM the best, coming from XFCE/MATE/Cinnamon.

I have been working on a minimal browser in C, focusing on security and local control. I wanted a browser where I could strictly control network access (Zero Trust) and sandbox the renderer using seccomp and landlock, without the bloat of modern engines. It is still in alpha and lacks full layout support, but the core sandboxing and IPC logic are stable. I am sharing it because I am looking for feedback from people interested in low-level security and systems programming. Here is the repo if you want to look at the architecture: [github.com/grisuno/FreeDom]

struct Monitor {
	...
	unsigned int seltags;
	unsigned int tagset[2];
	...
};

I'm struggling to understand .seltags and .tagset in Monitor struct. Like what is a tagset and why are there two of them?

Hello.

I've been participating on suckless and LISP communities at the same time, and ugh... just wanted to ask a quick question: do you consider Common Lisp suckless? And its ecosystem?

Thanks.

Last month a storm knocked out power in my area for most of the day. My desktop computer was useless, my home server was offline and even my internet connection disappeared after a few hours. All I had was an old ThinkPad with a nearly full battery and a minimal Linux installation that I had set up years ago as an experiment.

I expected to spend the day frustrated and unproductive. Instead, something surprising happened. That old machine booted instantly, used almost no power and had everything I actually needed. I could edit text, read documentation I had saved locally organize notes and work on a small programming project without any distractions.

As the hours passed I started comparing that experience with my main computer. My primary system had become a collection of conveniences layered on top of conveniences. Every task seemed to involve another application, another service running in the background or another tool that promised to save time. Yet during the outage I was getting meaningful work done with a fraction of the software.

When the power finally returned I looked at my regular setup differently. I spent the next weekend removing programs I rarely used simplifying my workflow and keeping only the tools that solved real problems. The result was not just a faster system. It felt calmer. There were fewer decisions to make and fewer distractions competing for attention.

That experience made me realize that simplicity is easiest to appreciate when complexity suddenly disappears. Sometimes it takes losing access to everything extra before you notice how little you actually need.

Has anyone else had a moment where a hardware failure outage or unexpected limitation completely changed the way they think about software?