Take you expected costs, double it, then throw the piece of paper way because it's still useless.

That drive me up the wall. Why have an entry level phone? the manufacturing costs between 16 and 64 is tiny. Why support some many phone types? just make 1 64GB phone.

And I ask the in earnest. What data support the cost of different lines vs/ the cost of all of them being 64GB?

what is crappy about it?
How does it relate to autocorrect software?

Texas can't secede. The original agreement was changed decades ago.

Never go full retard. X is not even remotely as important as init. For one thing, if X dies, who will restart it? And do we really want computers that explode when the GUI dies? I, for one, would like network services to terminate gracefully. The whole idea of TCP/IP networks, the dominant network used with Unix, is peer-to-peer. I may well run both services and clients on my machine. If X dies, the clients may die (if they're not text and running in screen) but the servers won't.

So the argument is that since the kernel is complex, we should add more complexity, or that more complexity won't matter? That's an ignorant, illogical argument.

Systemd still has to be more complicated so that it knows how to run these other processes, which wasn't even necessary. init was never meant to manage daemons. daemons were meant to manage themselves, or be run from inetd. If you want more complexity, inetd is the place to add it. And for handling daemons which don't adequately manage themselves, there's daemontools. There was simply no need whatsoever for this to happen.

It is bad, because PID1 is now responsible for a bunch of things which could have existed in any other daemon. And rather than roll the things which actually make sense in together, everything is getting rolled together. So now not only do we depend on a complex kernel, but we depend on a needlessly complex init system. There was no good reason to put all of this stuff into the same daemon.

Yes, yes I can. And I did.

Does nothing a script can't do

Systemd doesn't even fucking use capabilities, just cgroups. Which we could use before systemd. Systemd manages permissions in lieu of using capabilities, e.g. apparmor or selinux.

No. That is the virtue. They are simple. Simplicity is still a virtue.

Making PID1 more complex makes everything more fragile and opens up security holes.

NIH

This is making init do stuff it doesn't need to do, which makes it more complex, which makes it more fragile. You should not need a detailed explanation to understand why this is a bad thing.

Lifting which should not be done by PID 1. And PID 1 has to be more complex than it should be just to handle those external programs.

It does a lot of stuff the init system shouldn't do.

cgroups existed before systemd.

Up to the init script.

Already handled by several init systems.

We call it inetd.

That is ignorance at best, or perhaps a lie.

You have no idea about anything, that didn't stop you. I see why you didn't log in.

Turns out, that's not true.
Arming locals in an unstable environment has been the continuing problem with all modern conflicts in the mid-east.

It kind of made sense in the 50s, when the government was reasonably stable and before religious zealots started getting government power.

I like you assumption that all Muslims want holy wars.
Also, that ISIS rule the mid east and Africa would somehow not impact anyone else.

As for FDD... standard on the east coast USA and many other parts of the world. It works for unthinking peons but utterly fails for jobs that require imagination.

If you treat your employees like unthinking peons, they will respond by behaving like that - and that means turning a blind eye towards the innumerable small irregularities and problems a workforce that doesn't actively hate you could easily correct before they have a noticeable effect on production. That is the difference between workplaces where everything seems to work as if by magic and one that does a passable impression of being haunted by an evil spirit because it is, specifically yours.

There are no jobs that don't benefit from thinking about how it fits to the bigger picture.

But if you're afraid to do your job, it's because you have a problem with confidence in your own skills. Blaming management for such fears just takes the incompetence you exhibit to a whole new level of blame-gaming.

Unless it's not just you, but every one of your fellow employees. Then the problem is systematic in that workplace, and thus must be in the system itself.

The thing is, managers are humans and sometimes have serious issues or even outright mental problems, such as ego too powerful for them to handle. And sometimes they're simply afraid of their superiors. Competence only matters in a healthy organization where everyone is trying to meet its goals; in an ill one they concentrate on covering their ass, not just against mistakes but also against backstabbing.

So to be clear, it's more awful to have 1 out of every 9 people have to pass two people if they want to use the bathroom than to have 2 out of every 6? Because that's typical economy seating plans are 3-3.

It's not a religion, it's a principle. When it makes sense, you put it aside and get work done. The argument against systemd is that it doesn't make sense. systemd is a simple case of NIH because it provides absolutely nothing which could not be implemented with the existing daemons and some small shell scripts.

That's right.

That's not the complaint. The complaint is that the process at PID 1 should be simple. You people running around screaming about a bunch of different processes are only compounding the proof that you do not understand Unix. It's not a problem to have many processes.

It seems like you're extrapolating from that experience, to thinking "FDD" is a current trend. AFAIK it's not.

Sure it is. What's happening to programming is what happens to anything when there's more supply than demand: a race to the bottom. Personal computers used to be rare, so programmers could rely on their skills being so as well; now they're ubiquitous, and the industry is entering the same phase others did during the Industrial Revolution. The only known solution is to unionize and bargain collectively, but of course that requires giving up the cherished illusions of being able to make it on your own.

Bullshit, they're still letting licensed commercial vehicles use the HOV lane. The fact is that HOV lanes are shit. They're a waste of space which accomplishes none of the stated goals. Simply adding another general lane does more to reduce emissions, because it does more to reduce congestion, and thus reduces idling — where vehicles without start-stop systems get 0 MPG and thus are producing pure pollution. They're always trying to justify the existence of HOV lanes with bullshit like this, but they still are unjustifiable.