undefined | Better HN

0 pointsviraptor4y ago0 comments

Pipewire uses a different architecture than pulseaudio. It's basically "we learned lots of things from low-latency video, let's apply that everywhere", not a refactor.

What do you want to change in systemd specificaly?

0 comments

m4634y ago

one bit of relevant information to add to my comment:

The guy who wrote pulseaudio also designed systemd.

Since pipewire seems to get rave reviews, and pulseaudio grumbles... a natural train of thought would be - get the guy who wrote pipewire to take a stab at systemd.

As to specific systemd changes, I would love if someone:

- Make the systemd config files more intuitive. While the old /etc/init.d/foo files contained arguably too much logic, the systemd service files are stupid enough that logic frequently has to be pushed into (and hidden inside) a daemon.

change the awful directory structure/files/links to something more elegant and organized It's like they threw them all in one directory, and simultaneously sharded them across /etc /lib etc

status commands/journalctl/binary log files. ugh.

How has it absorbed so much into itself?

It's become a little like busybox - making an analogy here - where it absorbs tried-and-true utilities and replaces them with "good enough" that... isn't. One example might be NTP which does time sort of poorly. Yes ntp is crufty, but it does time extremely well.

viraptorOP4y ago

> a natural train of thought would be - get the guy who wrote pipewire to take a stab at systemd.

Alternative train of thought - Pottering was not great with low latency stream processing, but someone else was. Why expect the people who are good with low latency stream processing to be good with low-level process management? People have different skills/interests.

j / k navigate · click thread line to collapse