Hacker News new | comments | show | ask | jobs | submit login

I've recently came across this: http://bsd-geek.de/FreeBSD/NO_POETTERING.patch

I don't know (and doubt) if it got merged into FreeBSD, but it shows that lots of people just hate him.

I don't really see any hatred there.

Software he has been significantly involved with has caused problems for a lot of people in the past. The recent strife and disagreement surrounding systemd surely hasn't helped the situation.

If somebody has had bad experiences with multiple software systems developed by a particular developer/project/organization, it's totally understandable why they'd want to avoid that developer's/project's/organization's software in the future. Nor is it unreasonable to want to protect oneself in such a manner. Furthermore, this can be the case without holding any sort of hateful emotions toward the developer/project/organization in question.

Do you have a better name for such a flag that may not involve his name directly? It does seem like a very descriptive name for what it does, even if some people may incorrectly interpret it as being "hateful" or something like that.

I hate him because I had to spend some time fixing my sound, which had been working fine before, not for personal reasons. I don't think I'm being unreasonable.

Hating somebody for writing free software is not anywhere near reasonable. He never forced you to use it.

Read lmm's comment again. His dislike clearly arises from the problems this software has apparently caused him in the past.

I don't think it matters if the software in question is open source or closed source, or if it was obtained for free or paid for, or how the developer was compensated, or if it were developed by an individual or an organization, or why lmm had to use it in the first place.

Causing people unnecessary grief will invoke a negative reaction. That's perfectly understandable, and quite reasonable.

The main problem was that a particular popular distribution made PulseAudio its default audio system before it was ready for that, and did a bad job integrating and testing it.

That wasn't Lennart's fault. PulseAudio is a really mature and stable system now.

I disagree. PulseAudio is a prime example of Lennart confusing an issue that is fairly specific to Linux to an issue general to Unix. Other Unixes have solutions to the problem of a limited number of audio channels; in such places, PulseAudio only adds needless complexity. Had Lennart instead worked with the people of the Alsa project to improve it, we wouldn't have had any of the problems we saw with pulseaudio, and we wouldn't have yet another layer to deal with in handling audio.

He aggressively promoted it and got downstream applications and distributions to adopt it, no?

Wow. Well, that doesn't seem to be part of the FreeBSD ports tree as far as I can tell (at least not in this snapshot here).

What a sad idea..

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