3 ms·
It already has taken over despite being mediocre at best. Mostly I feel that it got an undue jumpstart thanks to RedHat trying too hard to be bleeding edge, an
by na85 12y ago
It already has taken over despite being mediocre at best.
Mostly I feel that it got an undue jumpstart thanks to RedHat trying too hard to be bleeding edge, and Upstart/OpenRC not having as high-profile a backer.
- gtaylor 12y agoTo be fair, Upstart was pretty awful in the early goings. It seems to be a lot more reliable and predictable now, but that's a fairly recent development for us (when we upgraded to Ubuntu 14.04 LTS).
- cbsmith 12y agoThe golden rule of technology hype: once people start abandoning a technology is when it starts being functional.
- dredmorbius 12y agoThe fact that upstart is covered under Canonical's developer contribution agreement and copyright license counted materially against it in the Debian debate. Canonical's insistence on control and ownership ended up torpedoing its project. Which is really quite sad.
- edwintorok 12y agoThe problem is that some projects started depending on systemd behaviour now and the transition hasn't been smooth at all in Debian even if you want to stay with sysvinit. I'm still on sysvinit with systemd-shim, and things started to break in KDE already, mostly related to authentication (can't mount USB devices, can't manage VPN connections, etc.). In the end I'm afraid Debian users might not have much choice: either use systemd as PID1, or use another distribution (like Gentoo, etc.) that work without systemd.