3 ms·

> When we talk about an OS that on desktop has minuscule user share, it is not too clever to further fragment that. True, but desktop usage is only one of many

> When we talk about an OS that on desktop has minuscule user share, it is not too clever to further fragment that. True, but desktop usage is only one of many things linux is used for. All the "unification" efforts ala systemd try to handle all of those use cases. I don't see why the init system on my server has to be the same as the one on my ultrabook, because only a fraction of what they should do is shared. Having one tool that covers all the use cases just sounds like a very good way to increase the attack surface. > I believe there are only a handful of people who knows enough to create a proper init system (similarly, sound and graphics) and do it for the community. I don't think Linux graphics or sound situations have much in common with the init system situation, except perhaps the fact that Poettering tried to fix sound as well.

kaba0 6y ago
> I don't see why the init system on my server has to be the same as the one on my ultrabook, because only a fraction of what they should do is shared Well, not even the kernel should be shared —- but most of us is okay with having the same kernel, but at most configured differently. I see it the same way in the case of systemd, of course your ultra book doesn’t need I don’t know how many services, but the basics are very much the same. And to be honest, I’m happy to use the same knowledge/tools on a server machine and a laptop. > Having one tool that covers all the use cases just sounds like a very good way to increase the attack surface. That’s just security by obscurity...