I've been migrating to nixos. I think it makes news in that everyone is obligated to hate it publicly for at least 6 months before resigning themselves to it.
Have you tried nixos? Its a totally different paradigm and definitely an acquired taste, but I used gentoo for ~2 years, then used Arch for ~5 and now am switching everything to nixos.
Main benefits is setting up a new machine is much easier, and updates are easier because almost all the normal configuration is managed by nixos (in the nix language) as opposed to regular files floating around etc.
I cycled through dwm at one point. The thing that killed me was that on my nvidia machine, for some reason it would flash when I changed desktops, like the draw order was wrong. i3 is the only tiling window manager that didn't, I think because it uses xcb instead of xlib.
I love the magical bullshit in the description. Each line contains some face palm.
> dwm doesn't distinguish between layers: there is no floating or tiled layer. Whether or not the clients of currently selected tag(s) are in tiled layout, you can rearrange them on the fly. Popup and fixed-size windows are always floating, however.
Ok so it does have floating then?
> Because dwm is customized through editing its source code, it's pointless to make binary packages of it. This keeps its userbase small and elitist. No novices asking stupid questions. There are some distributions that provide binary packages though.
Ok so you can package then....?
> dwm is only a single binary, and its source code is intended to never exceed 2000 SLOC.
Strange flex but ok.
> dwm has no Lua integration, no 9P support, no shell-based configuration, no remote control, and comes without any additional tools, such as for printing the selection or warping the mouse.
It uses x, x warps the mouse.
> dwm is customized through editing its source code, which makes it extremely fast and secure - it does not process any input data which isn't known at compile time, except window titles and status text read from the root window's name.
ok so there is input that could hacked (not saying there IS, but if you process strings or floats from the user those can contain unexpected values).
All that said, suckless tools are nice, just think the mindset is hilarious.
Its a slow to compile idiom. The only reason to use it is if you expect people to download the header and plop it in. Basically its an end-run around build systems.
The fu? This guy has no idea what he is talking about.
> there are also lack of technical knowledge at linux side, for example, most linux distributions cant even detect the cpu type, and force a kernel using PAE or SSE kernel on a 6x86 cpu, which of course will crash at boot.
Uh yes it can? cat /proc/cpuinfo? What he is saying (incorrectly) is that Linux is compiled for i686 -- which it often is, so that you don't get illegal instructions when you run programs. No one is preventing you from recompiling with optimizations and -march=native.
Theres so many levels of crazy in just the first paragraph.