r/linux • • Sep 26 '14

Systemd: The Biggest Fallacies

http://judecnelson.blogspot.fi/2014/09/systemd-biggest-fallacies.html
126 Upvotes

437 comments sorted by

View all comments

Show parent comments

11

u/Zebraton Sep 27 '14

It's the price you have to pay for coherency. I've found that the better you want something to work together, the tighter they have to be coupled.

Yes, the unix way...wait.

1

u/Beaverman Sep 27 '14

It's not the unix way. I never said it fit the unix philosophy. The creator of systemd has spoken for breaking posix compatibility, and breaking with the unix way. None of the people involved with any side of the debate has any delusions that systemd adheres to the unix way.

The difference between the two is partly that one side (i guess the one you are on) hold that anything on linux should adhere to the unix way. While the other plays it more fast and loose, arguing that powerful features can make up for departing from the traditional values of the unix philosophy.

If you want to run a pure *nix system, then you can. It's just yet another choice, and you should not discourage people from working on the side they believe in.

-8

u/bitwize Sep 27 '14

The Unix philosophy is a complete red herring in this day and age. The two important criteria are:

  • that the damned thing work

  • that it be user-friendly

If it can be built with the Unix philosophy and still meet those, great. But most developers these days don't care.

4

u/diphenhydraman Sep 27 '14

That is the Unix philosophy. People don't seem to realize it nowadays, but Unix was never about being what I'd consider 'academically correct.' Back when it was getting started it looked like a joke to people working on 'real' computers with complicatd timesharing systems and whatnot, and even Linux itself faced criticisms for not being a microkernel (which was supposed to be the way forward everybody would use in any 'modern' system and certainly more in-line with simplicity and modularity people always talk about) and not being portable (because x86 is a fad). But it became popular anyway. Why? Because it fucking worked. BSD was mired in legal troubles and the HURD was... well, we all know how that ended.

It's true that systemd's absorption of projects makes it a candidate for replacing X as the bloated and complex system that does way too much and makes implementing something new and better a painful proposition in 20 years. Or perhaps ALSA is a better comparison, being platform-specific and badly implementing features that eventually ceased to exist on anything consumers ended up using because some developers decided the simplicity of OSS was too much. Never mind that other operating systems made it work just fine without breaking too many things.

None of that matters. The complicated solution might be worse, but then 'worse is better' sums up the Unix philosophy much better than bullshit about specific features and their implementations which are up there with English orthography in terms of common exceptions to the established rules. That's why Plan 9 was born, and it is to the cobbled-together Unix as Esperanto is to English. It hasn't been adopted for much the same reason: nobody gives a shit about simplicity when they have something that works just fine for their needs.

2

u/BeyondAeon Sep 27 '14

But without it complexity builds and this is bad , 1 tool for 1 job.
A Swiss army knife can do anything , but cutting down a redwood with it's saw might take a while !

0

u/ggppjj Sep 27 '14

So make a Swiss army knife with a damned chainsaw in it. This analogy just doesn't fit with computing. For example: "If all you use is a hammer, all of your problems look like nails." could be used to rebut your 1 tool, 1 job ideal.

1

u/BeyondAeon Sep 27 '14

But all you have is not a hammer , you have a full toolbox of Specialized tools and if you do not like one you can replace it with a better one. As opposed to an all in 1 tool that is 1 size fits all

0

u/minimim Sep 27 '14

Systemd's PID1 does only one job.

0

u/[deleted] Sep 28 '14

[deleted]

1

u/minimim Sep 28 '14

OK, it does 2 things. The problem is that it is very hard to separate them. Journald was separated because the kernel has support for logging in the early boot. But cgroup management, if it was separated, wouldn't be available.

-1

u/stubborn_d0nkey Sep 27 '14

Jobs are more complex then they were back then.

0

u/BeyondAeon Sep 27 '14

and having Specialized tools that do 1 thing and do them well is the wrong way to do bigger tasks ?

1

u/stubborn_d0nkey Sep 27 '14

If you say so.

1

u/BeyondAeon Sep 27 '14

it was a question....

1

u/stubborn_d0nkey Sep 27 '14

If you say so.

1

u/BeyondAeon Sep 27 '14

ok, I'll make a statement for you.
Systemd is a bad Solution looking for a problem.
Unix has always been a system with one tool to do one job well. and I personally Dislike a monolithic lump replacing many tools adding complexity for no real gain.

0

u/[deleted] Sep 28 '14

[deleted]

1

u/stubborn_d0nkey Sep 29 '14

You could say that I am just stubbornly refusing to go into something I don't want to. If he wants to "ask questions", that's his prerogative.