←back to thread

466 points CoolCold | 4 comments | | HN request time: 0.478s | source
Show context
jacoblambda[dead post] ◴[] No.40212554[source]
[flagged]
1. IntelMiner ◴[] No.40212625[source]
You're always welcome to write an alternative if you don't think systemd's direction is correct. Frankly with the number of detractors you could likely form a much larger team to "do it properly" instead!

Love or hate Pottering and his team, they're at least writing code instead of postulating on internet forums. systemd's adoption and popularity among many is proof of that

replies(2): >>40212663 #>>40215699 #
2. ranger_danger ◴[] No.40212663[source]
> instead of postulating on internet forums

Love or hate internet discussion, you're always welcome to not participate in it.

replies(1): >>40214226 #
3. IntelMiner ◴[] No.40214226[source]
To your point. Lennart instead of participating, just writes code? :)
4. jacoblambda ◴[] No.40215699[source]
> You're always welcome to write an alternative if you don't think systemd's direction is correct.

They actually exist. Namely OpenRC and s6 as the main competitors to the core systemd functionality (init). There exist other alternative projects for the other components of systemd as well.

My complaint is that they are adding another tool that depends on their core software in an attempt to replace a portable, well established tool in a non-drop-in way.

This is a consistent pattern with systemd that feels very embrace-extend-extinguish-y and it does nothing but increase the cost involved in keeping code portable between different platforms.