Who modded this up?

Formal code testing is pretty much what Redhat brings to the table.

At worst it breaks their startup scripts, and since they are shell scripts they are easy to fix.

Do you really understand the architecture of either SystemD or sendmail? Sendmail was a single binary written in a time before anyone cared about security. I don't recall sendmail being a bundle programs but then it's been a decade since I stopped using it precisely because of it's poor security track record. Contrary to your FUD, Systemd runs things as separate daemons with each component using the least amount of privileges needed to do it's job and on top of that many of the network services (ntp, dhcpd) that people complain about are completely optional addons and quite frankly, since they seem designed around the single purpose of Linux containers, I have not installed them. This is a basic FAQ entry on the systemd web site so I really don't get how you didn't know this.

Unlikely, it is a minority of malcontents who are upset about SystemD who have created an echo chamber of half truths and outright lies. Anyone who needs to get work done will not even notice the transition.

Again you use the word "monolitic without having a shred of knowledge about how SystemD works.The previous init system despite all of it's testing was a huge mess. There is a reason there were multiple projects that came before SystemD that tried to clean up the horrific mess that was the previous init.

Solaris has already transitioned to it's own equivalent daemon that does roughly what SystemD does.
As for SystemD: It allows booting on more complicated hardware. Debian switched because they were losing market share on larger systems that the current init system only handles under extreme protest. As a side affect of the primary problem it was meant to solve, it happens to be faster which is great for desktops and uses a lot less memory which is good for embedded systems.

Riight.. Meanwhile in the real world, none of my desktops or servers have any SystemD related network services running so no root hole here.

The big issue will be that people will use this to display rude things on random people's armbands.

You want to bet that number subtracts the cost of their network build out from the profit margins? The bulk of the costs are the labour and equipment needed to run the fiber. Once the fiber is in place, upgrades are just a matter of swapping out the equipment at both ends and the costs will drop sharply.

They are making money, it's just that internet is less of a profit center than wireless so they would rather put the money where they can make the higher profit.

Your plan falls apart when you have large groups of people who are willing to believe literally anything about some group they don't like and refuse to accept any evidence that they are wrong.

The number of people who believe Obama will bring in Sharia law or has the national guard preparing internment camps is outright staggering.

That's pretty interesting considering it was designed for servers to begin with. Servers are far more likely to have weird dependencies on boot such as root drive over the network or worse yet, boot drive over clustered file system over the network and where Debian said they are losing share due to not being able to support some of the larger server configurations.

For the embedded space, it either uses less memory than the current setup, or you are rolling your own init and don't care about systemd at all.

You do realize that most of the systemd addon daemons run
1. As a completely separate process
2. With the minimum permissions need to do their job.
3. The stuff with network connections are definitely optional..

I know they have some network things that they optimized for containers but they don't seem general purpose so I don't run any of them on the servers I'm testing systemd on. So far the only actual Systemd issue I've had is that it screws up pulse audio on one of my machines (works fine on the laptop screws up on my desktop).

Mainly because the market is very price sensitive and as a result routers tend to use some slow SOC with a minimal amount of RAM because it costs less. Linux or BSD wouldn't do you much good if every time someone fires up bittorrent, the NAT table fills because there just isn't enough RAM to handle it all. It has only been recently that I've seen routers with a decent amount of ram and even then that has been in the $150+ range while most people I know refer to spend $30 to $40.

A few years back my friend went to get his BMW from my garage where he had left it for the winter only to find a flat tire waiting. I thought "no problem" we can just use the spare just as my father taught me. We pull the jack out that came with the car and attempted to jack the car up but the jack actually started to collapse under the weight of the car. At that point we gave up and called CAA and when the guy arrives says "why did you guys try to do this yourselves?" It seems the jack was mostly decorative.

Throw in modern cars with diagnostic readouts proprietary to the car and you find a car that is simply not designed to be repaired by anyone other than the dealership so don't blame training or our generation for the problem.

You might want to reread that. It's not supporting it, it is just ignoring the certificate error and indexing the site anyways. On the plus side it will work by accident as long as you don't tell apache to redirect to an error page on SNI failure. So it's mostly good news.

Bing and Yahoo's web crawlers do not support SNI so you can enable it as long as you don't mind not being indexed on some search engines.

Which is why it was really sad when chrome backed off on supporting DANE

Uh no, the Linux kernel is monolithic because it runs the drivers as if they were a part of the kernel rather than running the drivers as separate processes.

It isn't in the actual init system, it is an optional daemon that uses the interfaces that systemd exports so there is nothing that actually forces anyone to use it. My Debian based firewall runs systemd with unbound without any problem.

Did it actually not boot or did it seem to hang and the guy resets it after a minute? I ask because my PC had exactly this problem. Ages ago I had a drive die in my system so I pulled it but missed one of the references in /etc/fstab and when I did the initial conversion to systemd it hung and I was about to pull my hear out but instead I left the room to clear my head and came back several minutes later to find my system booted with no explanation as to why the delay.

The systemd update a few weeks ago finally gave me a nice message on console to let me know that one of my fstab entries was timing out so I checked, found the entry and now everything boots faster.