Also in regards to kernel development, monolith is a overloaded term.

  A microkernel shoves as much crap into user space as it can, a monolithic kernel does not. It doesn't mean its architecture has to be monolithic, the Linux kernel is proof of that.

For all of the different processes in systemd, they might as well be shoved in one process because that is exactly the effect that it gives having all its processes tightly coupled to each other.

If people could pull out BS like the logger and login and seamlessly add their own sane processes, the complaints would mostly disappear. Instead, you have to take the binary logger and use that buggy mess to forward it to a sane text logger.

If you systemd apologists can't see how any of this is poor design and detrimental to linux you simply lack the technical knowledge and should stop white knighting for that idiot poettering.

The Linux kernel is monolithic in design but modular in architecture.

Systemd is the opposite and is the wrong way to approach it.

ls and cd are programs

new lines are free ya know.

"Cloud" computers are servers.

It is amazing that people think that a distributed mainframes are something special.

A lot of the time a "cloud" service is an overpriced VPS and nothing more.

Yeah, more functionality that I don't want or need. A binary log system is beyond stupid. It is Microsoft registry levels of stupid.

It is like paying $50 for a cable package of 75 channels when I only watch 3.

You obviously do care. Tell me, what are you getting for your shilling? It must be doing something for you else you wouldn't be doing it.

That was terrible. Poettering is such an ass clown.

His only defense was 'it's free'. Well, that is no excuse for making overly complex, poorly implemented programs.

So what you are saying, to get the original functionality back you have to add more complexity?

Do you systemd fanboys ever stop and listen to yourselves?

You can not copyright the ingredient list in a recipe.

You can copyright the instructions.

You entire post was wrong. The twat in question is not part of the crew. Posting complaints about said twat is not threatening or abusive and she was wrong. Even SWA eventually admitted she was wrong by saying that all comments about their service, good or bad, are welcomed on "social media". Hopefully she got fired or demoted to a position where she doesn't have to deal with customers.

My point about you being a coward stands.

Go hide under a rock, it is safer for you.

You are truly stupid.

There is no such thing as an ad hominem attack. It is a fallacy that have nothing to do with calling you names. Trying to defend yourself by misusing the term is the hallmark of the willfully stupid, which you stand as a proud member of.

It is a term misused by morons like you, who get called out for being a moron, when all that happened was that you were insulted.

One more time since you are stupid: An ad hominem is not the same thing as calling you descriptive and correct names.

If you don't want to be called out for being an idiot, at least learn what ad hominem means.

You must be a member of the participation trophy generation.

Yup, a proper chef knows how to accept criticism and if he is truly good will admit his cake is shit, and make an acceptable cake to replace it.

You, on the other hand, are a weeping vagina that needs to man up and take responsibility for your shitty cake.

No participation trophy for you!

The media whores at Southwest Airlines have a sense of humor:

Not only are you stupid, you are also a coward.

If that was intimidation to you, unplug the internet, weld your doors shut and brick your windows.

If she isn't fired, SWA has serious problems.

What breach of safety did this cause?

I truly hope that girl was fired for being a vindictive twat.

errr coating