[Accacin]

> Why is the solution more complex than the problem domain?

So, where's your solution? If it's so simple, where is your contribution?

The fact is, he did it. You haven't. I can't even begin to imagine how much crap Lennart gets everyday by people who think they know everything and yet never actually seem to write any code.

Have some respect for the guy even if you disagree with the way he works, because you know.. his code is being used.

[CameronNemo]

openrc, runit, s6, upstart*

dmix, jack, pipewire

* now maintained at https://gitlab.com/chinstrap/startup

[Accacin]

I mean, if anything your list proves my point. They're not used at all. Also, I was asking parent for his implementation - I'm assuming he hasn't written any actual code though.

[tomxor]

> I was asking parent for his implementation

This is not a valid argument, invalidating discussion of merit of thing based on not having personally created incarnation of said thing would remove 99% of debate of FOSS to no ones benefit.

[ravar]

Jack is actually really useful for music production, far superior to pulse audio, so yeah, people do use those programs.

[tripzilch]

My only problem with Jack is that Firefox (and Chrome too, afaik) absolutely insists on using Pulse, so you have to make both play nice if you want to use Youtube while working on music (which is actually pretty common). This can be a bit of a pain (funny things happen after suspend/resume). Still it's so useful for music/sound production, I put up with it :-)

[ravar]

Yeah I can relate to that, I start jack with qjackctl and run this post startup script "a2jmidid -e & pacmd set-default-sink jack_out "

[Accacin]

Fair point, I didn't know that.

[paulddraper]

Being popular doesn't make you right.

[bonzini]

Jack does not overlap with PulseAudio. Pipewire does, but it came later and has the explicit purpose of unifying Jack and PulseAudio.

Upstart is decidedly inferior to systemd; the event-based architecture is much harder to understand and apply than the target/dependency architecture of systemd. And systemd is in use in distros ranging from embedded (LibreELEC) to enterprise server, it must be doing _something_ right...

[CameronNemo]

Regarding the event driven architecture: it is far easier to understand than systemd's dependency system. But it is indeed more difficult to apply, particularly because it is a departure from how most systems work currently and in the sysvinit past.

I enjoy the architecture, and hope to continue developing Upstart/startup or at least work with a similar model.

[chris_wot]

And yet none of those init systems are really being used in any significant way. It doesn't detract from them, but then they don't detract from systemd.