News for hackers. Stuff that matters.
Re:Systemd Wants to Expand to Include a Sudo Replacement by jacoblambda on Tuesday April 30, 2024 @12:19PM (#40212740)
The issue is that it's not just ideological. "Do one thing and do it well" is important because if you want to port software to another platform, it's a lot easier to port a single dependency component over to make it work than it is to port over the entire framework.

This is a serious problem and it makes it way harder to make things cross platform.

Re:Systemd Wants to Expand to Include a Sudo Replacement by Xylakant on Tuesday April 30, 2024 @03:23PM (#40215134)
Systemd was written specifically for Linux, hard depends on a list of features provided by the Linux kernel and leverages them to do its work. Porting it to another kernel is a rewrite. Lack of portability is in this case a design tradeoff.
Re:Systemd Wants to Expand to Include a Sudo Replacement by jacoblambda on Tuesday April 30, 2024 @04:00PM (#40215607)
Sure that is the case for systemd itself but it's not the case for most projects that happen to use things systemd provides.

There is very little benefit for most userspace software to tie itself to systemd and by extension linux when otherwise it could be portable to any unix or unix like platform. Especially when an alternative, portable solution already exists and is well established.

Re:Systemd Wants to Expand to Include a Sudo Replacement by fhars on Tuesday April 30, 2024 @04:00PM (#40215608)
The argument was that this design of systemd makes it hard to write applications that are portable, so that systemd is effectively a very big net negative to the open source ecosystem, because it causes massive fragmentation.