3 ms·
With windows, (and I suggest systemd) you're either all in or all out. And as the scope continues to increase, you're still either all in or all out. As the d
by anotherhue 6y ago
With windows, (and I suggest systemd) you're either all in or all out.
And as the scope continues to increase, you're still either all in or all out.
As the distros fall into line, you're either all in or all out.
Try and not use systemd, and then tell me it's not a problem. I think it's honestly easier to not use windows at this stage. The BSDs (love them as I do) just don't have the clout or the support for many day to day developer needs.
- galgalesh 6y ago> With windows, (and I suggest systemd) you're either all in or all out. This is not the case with systemd. Although these projects live in the same repository, distributions can pick and choose them depending on your priorities. Granted, this is obviously not something most end users come in contact with and even know since very few people actually build distributions. As an end user, ripping out a core part of a distro to replace it is always a painful experience. Regardless of whether that component lives in the systemd repo or somewhere else. Systemd actually makes ripping out core parts easier, which is why arch adopted it so quickly, but that's another story. You're just throwing vague and incorrect statements out there, sprinkle "Windows" on top in the hopes of eliciting an emotional response.