IssueRaiser

Lennart is very good at the political wrangling required to get code into distros and make it an unavoidable part of using Linux.

Lennart is very good at the political wrangling required to get code into distros and make it an unavoidable part of using Linux. His actual code quality is not so great. PulseAudio is still a mess a decade on, and I gave up even trying to figure out why it breaks because it's a nightmare of misleading variable names and uncommented code. I finally abandoned hope when I tracked down a crash, found that a patch that was literally unfinished and labelled as such had made it into a release before being backed out, realised they don't do stable releases and the next upstream release with the fix would have other major changes with new bugs, and eventually discovered that reverting it didn't even fix the problem. The underlying code was simply broken and there was no way to see how it was ever meant to have worked in the first place, because it was completely uncommented. systemd seems to have slightly better code, probably because it has kernel developers on the team, but like PulseAudio there are no stable releases. It's up to individual distros to try and turn the stream of upstream releases into something that works. I think this is a Red Hat thing - they're happy to develop new features collaboratively and in the open, but actually turning software into stable, reliable working releases is their secret sauce that people pay them big dollars for. They're also the only major distro that doesn't co-operate with the upstream Linux kernel's process for stable and long-term releases.

Posted by makomk on Jul 1, 2015, 11:30 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

reliability (SaaS)

Lennart is very good at the political wrangling required to get code into distros and make it an unavoidable part of using Linux.

makomkJul 1, 2015, 11:30 AM

Lennart is very good at the political wrangling required to get code into distros and make it an unavoidable part of using Linux. His actual code quality is not so great. PulseAudio is still a mess a decade on, and I gave up even trying to figure out why it breaks because it's a nightmare of misleading variable names and uncommented code. I finally abandoned hope when I tracked down a crash, found that a patch that was literally unfinished and labelled as such had made it into a release before being backed out, realised they don't do stable releases and the next upstream release with the fix would have other major changes with new bugs, and eventually discovered that reverting it didn't even fix the problem. The underlying code was simply broken and there was no way to see how it was ever meant to have worked in the first place, because it was completely uncommented. systemd seems to have slightly better code, probably because it has kernel developers on the team, but like PulseAudio there are no stable releases. It's up to individual distros to try and turn the stream of upstream releases into something that works. I think this is a Red Hat thing - they're happy to develop new features collaboratively and in the open, but actually turning software into stable, reliable working releases is their secret sauce that people pay them big dollars for. They're also the only major distro that doesn't co-operate with the upstream Linux kernel's process for stable and long-term releases.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue