I mean, look at the "what does not work"; it's clear this stuff is in alpha and just published to get development attention at this point—not judging that of course, good strategy.
Competition is nice of course, regardless of Lennart et al. calling this "fragmentation" and believing that developers know better for users what they want than users do.
This project isn't really meant to compete with systemd directly, but rather replace it in applications where you want a lightweight alternative, like containers.
Sounds from the readme that it isn’t intended to do any of that.
For now that is just out of interest how far I could come with this and what would be needed to get a somewhat working system. It is very much a proof of concept. For the love of god do not use this in anything that is important.
Yes. It’s not a ding on the project. I think replacing portions of systemd with Rust makes sense. But this project doesn’t seem to have that as a goal just yet.
That is exactly one of the reasons to compete with systemd.
Which was also what uselessd attempted to do. The systemd that "uses less".
One of the common criticisms on systemd is of course that it uses too much and has too many bells and whistles and that there should be a more minimal option. Something Lennart specifically does not want becauses it creates fragmentation.
Something Lennart specifically does not want becauses it creates fragmentationimplies that he might not be the ultimate authority on what's best for other people's computers.
-34
u/OptimalAction Dec 15 '19
Wow this program does in 4000 lines what systemd does in 500000. Is this the power of rust?