3 ms·
systemd desperately needs competition. it isnt just that it became a dependency for every low level service and a potential vector for privacy invasion, it's al
by pydry 4mo ago
systemd desperately needs competition. it isnt just that it became a dependency for every low level service and a potential vector for privacy invasion, it's also janky to use.
- fragmede 4mo agowhere is it janky?
- youre-wrong3 4mo agoHis imagination.
- shakna 4mo agoThe output devices (/dev/stdXXX) being sockets-only constantly trip people up.
- egorfine 4mo ago> systemd desperately needs competition Maybe it's too late. LP is cooking a way to deny system modifications [1] [1] https://news.ycombinator.com/item?id=46784572 https://news.ycombinator.com/item?id=46784572
- matheusmoreira 4mo agoI do agree it needs competition. The more the better. The dependency thing is bad but it's free software. It will always be possible to route around that if it ever turns into a problem. Especially now that we have LLMs. I don't think it's janky though. It's pretty great. It has an answer to everything I've ever needed from it.
- tmtvl 4mo agoGNU Shepherd maybe?
- nubinetwork 4mo agoTry porting svcs from Solaris to Linux...
- jeroenhd 4mo agoI do agree that systemd could use some competition, but until someone builds one, we're going to be dealing with some systemd defaults. Canonical's attempts seem to have been most complete, but outrage at change and different ideas have shut down most of Canonical's attempts to improve the situation. It's far from janky, at least compared to what else is out there for Linux. If you're not writing systemd service files, you're almost surely back to writing unpredictable 80s style scripting jank.