Hacker News Reader

Comment by ilitirit | Hacker News Reader

> If you take a Sunday afternoon to study the code, you will very likely understand how every piece of the software works, at which point you will be in a position to fix anything you might find. You might even end up forking it and implementing your own window manager (AwesomeWM was originally forked from Dwm).

I don't think I have ever needed to do this "fix" any piece of configuration in any software.

While I understand the concept and approach, I don't think that this is a productive use of most people's time.

View on HN

Be a little charitable to OP and this reply. The configuration is indeed in code but it's macro defines. It's essentially as simple as changing a text configuration file, it's not like you have to actually edit code (as in new functions, adding actual logic). Things like fonts and sizes and colors is changing defines, it's actually simple.

Now when it comes to more complex stuff, like hotkeys, well you're essentially programming already in most other wms that doesn't have such things build in. AwesomeWM, i3, qtile (not popular but I used it for years) basically is half-way to programming, although it's a line, so it isn't any worse. I think the thing people aren't getting is the code is actually simple, so editing it and recompiling it isn't a chore.

I actually am quite familiar with suckless tools and I do consider myself an advanced user, so I'm probably part of their target market as well. But to be honest, from a pragmatic point of view I just don't see how configuration through code is better/worse than configuration through dot/json/ini files in the average "suckless" use-case. Why must this even be something that I care about?

If it's a case of their software being simpler to understand so which makes it easier to fix bugs, then sure, I get that. But in my experience, software that has been around forever just tends to have fewer bugs in general so it's also just something else that I simply don't need to care about. And how often does the average user of suckless tools actually have to fix bugs in the programs? If it's more than once, then does the label "suck less" even qualify?

Is it just because the software is extremely minimal and therefore less "bloated"? I get that too, but personally, why would I care if a piece of software is 70kb or 500kb in this age? YMMV.

Don't get me wrong - I'm not trying to bash suckless or any other community here. I'm just very pragmatic about the tools that I use and my workflow. If you're the type of person that likes to tinker and customize every aspect from the ground up, sure then maybe suckless tools are for you. Tinker and mod away, there's absolutely nothing wrong with that.

> I get that too, but personally, why would I care if a piece of software is 70kb or 500kb in this age? YMMV.

I'm torn on this because I am way, way over screwing around with my OS, but I also hate that all the modern standard desktop operating systems (macOS, Win10, Gnome3 or KDE) that you get if you don't want to jack with defaults and configure things or use some way-less-popular so likely to be (even more) janky distro or "spin" or whatever, want to take up a gigabyte or more (way more for macOS and Win10 especially, tens of GB) of disk and hundreds of MB of RAM, while delivering experiences that are marginally better than what we had in the late 90s and early 2000s with sub-GB OS installations and low-tens of MB of memory use when idle.

All the more reason to not get worked up over including something as mundane as a TOML parser in your dependencies for a config file. So that, you know, you don't have to recompile your WM whenever you want to adjust something.

Personally, it's a hugely productive use of my time, if I didn't have the ability to customize my UIs to work around my health issues I could code very little, or not at all.

I use Awesome WM which is configured / scripted with lua. I know lua already so it's great.

Have you ever used software with bugs?

Reply on news.ycombinator.com