Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> WindowMaker

That's my 2nd choice. It's simple, lightning-fast, with almost no memory footprint.

> bug=815586

That's a perfect example of the problem with the 0pointer monoculture. I works great, until you do something slightly more complicated. Of course, the suggested fix is to update to a newer version of systemd. I guess you're out of luck if that newer version has compatibility issues.

> their own favourite toolkit again

I guess I never cared much about looks. Looks and feel is important, but "working" and "not crashing" are far more important.

One of the problems we're seeing is that the concept of the "distro" is largely dead. The damage done by systemd/etc wasn't just the bugs like your [1]. The forced monoculture killed the idea of different distros.



> Of course, the suggested fix is to update to a newer version of systemd.

That's actually a boilerplate Debian bug closure message, mail-merged with the bug number, the maintainer's contact information, and the package's changelog. One can find it at the bottom of many Debian bug logs. The suggestion really comes from Debian.

Moreover, the bug was in the "unstable" version of Debian, i.e. a version of the package (229-1) that had not even progressed to the "testing" version of Debian (which is currently at systemd version 228). Debian's policy on bugs in "unstable" can be read on Debian's WWW site at https://wiki.debian.org/DebianUnstable and https://www.debian.org/releases/sid/ .

The Debian message is, as mentioned, simply robotic Debian bug-tracking-system boilerplate. The underlying systemd bug reports have stuff written by actual human beings:

* https://github.com/systemd/systemd/issues/2572

* https://github.com/systemd/systemd/issues/1866




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: