What did Debian do to you?

>>314701
so what did niri do right that debian didin't

>>314702
systemD is enough...

>>314703
Profile picture checks out I guess

>>314704
Literally no reason to care about systemd’s presence. It makes absolutely no difference to the end user

>>314705
This is a misinformed comment. Of course it does. Maybe you cannot use something outside systemD but when my systems boots slower, uses too much ram, has so many bugs here and there and it is unsecure then how the end user is not affected by systemD ?

>>314706
Actually there have been a lot of benchmarks finding basically no difference in boot times, RAM use etc. between systemD and other init systems outside of a margin of error. There is also no evidence to suggest that it is buggier or less secure.

It’s not 2011 anymore, pal

>>314707
https://youtu.be/Cg8S47n7VQA?si=u-g_LuhGA-L6W8ZG

Check this and image what happens with every program you are using.

Also: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=systemd;dist=unstable

>>314708
That first test is pretty shit given that they used different distros. And all software has bugs. Your claim was that Systemd has MORE bugs relative to others. You can’t just compare systemd with another init system because systemd is not just an init system. You need to compare the number of bugs systemd has with the number of bugs another init system + the equivalent services has.

I’m also pretty sceptical of boot time being anyone’s concern in the big 26. Don’t you have an SSD? Those tests were done on a HDD. In the comments he said that on an SSD all boot times were the same

>>314709
You care so much about non-existent problems with systemd, yet you can't even bother to remove the real bloat which is Google's ?si= spyware tracker in your YouTube share link, lol

Go touch some grass, I love systemd. It works great, I keep all my stuff deployed on systemd services and I have never had a single complaint.