4 ms·
There are excellent reasons to ignore the UNIX philosophy. "Do one thing and do it well" is fantastic and resonates a lot with us, programmers. The truth howeve
by scrollaway 13y ago
There are excellent reasons to ignore the UNIX philosophy. "Do one thing and do it well" is fantastic and resonates a lot with us, programmers. The truth however is that this is not how an OS works.
systemd does a lot of things because the systemd project is tackling a lot of issues on Linux. And as any of us will know and have experienced, when refactoring something it tends to be very cascading. So systemd has all these inter-dependencies with tools and concepts that the same developers worked on. systemd-logind, systemd-journal, systemd-networkd, kdbus, etc etc.
Here's a fact: my systemd-powered machines have never worked so well and completely out of the box! These guys are doing amazing work, they are making Linux into a very, very serious competitor with today's desktop and mobile (incl laptop) machines.
They are doing the dependencies too tightly, yes. They don't care enough about the possibility of other people reimplementing parts of what they do. But their actual achievements are incredible. I have a huge respect for what they do.
That said... I have very little respect for them. The ability to separate a person from what they do seems to be a rare quality this way, despite what everyone claims (what with the Brendan Eich issue and such). The fucking attitude in these projects is disgusting. And these people don't actually understand that they are universally hated for behaving like children over such stupid issues. They live in a different world.
And this is all just what you see externally. Internally, it's free-for-all retardfest...
Fucking human nature, man. I've never been so uneasy as in the last few weeks... I can swear things used to be better but maybe I can just see things more clearly now.
- krick 13y agoI don't disagree with what you say, but it feels like a lot more important issue than you describe it. The whole systemd thing was intended to rewrite some pretty complex stuff that works already, but as it turned out over time does many things wrong. And do it right™ this time. Keywords: "rewrite", "already works", "right". And I personally believe it's a good idea, because what is done wrong at low level produces more and more work, complexity and errors on higher levels. Very hard to achieve, but essentially good. Now, the complex system with good API and architecture, but not-so-perfect internals is hard, but possible to fix and improve over time. System with bad API is essentially impossible to fix, ever. People that write optimal code without bugs, but terrible APIs and don't care about what others feel about that simply cannot "do it right™". Yeah, it may work well out of the box, but the progress goes on and after 5-10 years community will struggle to implement something new and important on top of that systemd and feel that only way to stop the pain is to replace it with some systemπ and do it right™, and people will remember 2014 year and say: "Well, we had that story with systemd already. It turned out to be no good! We'll make do without doing stuff right™." Thinking about it I feel sad regardless it may work smooth out of the box at the moment.
- scrollaway 13y agoI found systemd has a really good API tbh. What are your issues with it?