2 ms·
> brick the system in ways not even imaginable on regular init Init before systemd didn't do dependencies in most distros (or at least not in a serious way), s
by viraptor 5y ago
> brick the system in ways not even imaginable on regular init
Init before systemd didn't do dependencies in most distros (or at least not in a serious way), so this goes both ways. Systemd can get stuck waiting for something, but initd broke by YOLOing the startup and hopeing things work. There are good points for either approach.
The issue count though really doesn't mean much. What's the boundary of core even? gnome-shell has 1.1k open issues right now while systemd pid1 has 404 of them. Where does the 100 come from? Then the tagging, auto-closing, project management style, etc. come into play. It's a silly metric.