I think the big issue is the potential to use this as a vector to introduce malware to the phone or PC the owner interfaces the device with. Not sure how practical that is.
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.
PfSense is a must if you are running ESXi topologies.
SystemD hatred is pretty simple. A large amount of untested, potentially unsecure, unaudited code was placed at the core of Linux's userland, and forced on end users (enterprise IT shops) without any real testing or feedback by end users.
RedHat has bet the farm on SystemD... if/when it has security issues (it has network connections, so in theory, it can be remote rooted), it can cause a mass flight from RHEL and downstreams. The gain? Little to none, from the end user point of view.
I am keeping fingers crossed, and hoping someone forks the cash for an audit of the code... Oracle and Microsoft are waiting in the wings for mainstream Linux distros to fall on their face if something does break.
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).
It is easier to write an incorrect program than understand a correct one.
