Hacker News new | ask | show | jobs
by kevincox 1333 days ago
A developer that has been able to make tough choices and drive them well enough to get mass adoption?

He definitely isn't perfect but this sounds like quite the feat in Open Source.

2 comments

There is a huge difference between a developer who creates a superior project that everybody loves to use so it gets mass adoption and one who makes a product that gets pushed by their employer on everyone whether they want it or not. I don't want to get into details as the subject has been beaten to death but as for Systemd* there was the case of integration with graphical login that made choice difficult. Had the author been more sensitive to this issue and cooperated a bit without being stubborn we wouldn't have had Devuan and all that mess. This is exactly NOT the way to do things in open source.

*PulseAudio was simply broken but it's not the fault of the author distros picked up aplha-quality software

> This is exactly NOT the way to do things in open source.

Someone made a decision, others didn't like it so forked. Sounds like open source is working exactly as it should?

For applications, tools, even most libraries - yes. But this was one of the critical elements of the system and they had to fork the entire distro because the way it was done actually made the choice more limited.
>But this was one of the critical elements of the system and they had to fork the entire distro because the way it was done actually made the choice more limited.

This isn't very accurate. When Debian decided to switch to systemd, they also agreed to support other inits in the distribution.

This wasn't good enough, so Devuan itself was forked before this decision was made. The end result is that Debian had less people to support the init script alternatives. It became a self-fulfilling prophecy.

I'm confident Debian could support other inits if there was more Debian devs available to work on it. But because people left for Devuan the pool becomes smaller.

Even the last decision on inits from Debian says that the focus should not solely be on systemd.

https://lwn.net/Articles/808217/

> they also agreed to support other inits in the distribution.

That's true, but with systemd being the only init that packages had to support. Accordingly many package maintainers choose to only support systemd.

So if you want to run Debian without systemd, you have to be prepared for your fave packages to drop support for the other inits. It follows that you can't rely on the Debian package repository. So to support a Debian-like system without systemd, you have to fork the whole repository.

I think the situation would have been better if the people opposed to Debian would contribute to better init script support then just forking it.
> a product that gets pushed by their employer on everyone whether they want it or not.

Highly inaccurate

> A developer that has been able to make arbitrary choices and drive them thorough his employers connections to get mass adoption

FTFY