Purchasing it at retail rates sure as hell is.
This is all off topic and the poster you replied to wasn't correct, however...
A minority of the people actively embrace it; the vast majority accept it somewhat reluctantly and go with the flow; and an even smaller minority
The simple fact is no one has data here. Magically, whoever is bitching and moaning about the other side calls out the other side as the smaller vocal minority. Convenient.
systemd is a different beast than other decisions. RedHat historically caught flak (justifiably) for releasing distributions incorporating pre-release upstream builds in fundamental places. No one argued that the components were going to be the wrong direction, just that they weren't ready yet. Red Hat ultimately 'fixed' that by reserving their brand for 'enterprise only' and recalibrating expectations around Fedora. Pulseaudio despite being ubiquitous still has a lot of discussion on how to disable it when it just doesn't work right still. NetworkManager is also close, and also is accompanied by instructions on how to revert to the 'old' way. Same for firewalld. systemd is the first decision that really forces the issue in a fundamental way that's hard to avoid. This is strangely without precedent, for something so controversial to not be in a place that could conceivably be turned off by those who don't want it.
Bring back hypercard
Those cost more. This is lets throw something that you can buy on ebay for 50 bucks have it cost 5000 and break all the time. Dont forget were effectively paying for it though the massive subsidies so that long distance rail does not die.
Don't get me wrong putting in 300-600kph trains could do a ton of good for the US.
Check out your average tiny business, often a receptionist who might take email/phone bookings and put them into a web based appointment app on the same machine that is running the cash box and CC reader. Their PCI compliance is check all the correct boxes regardless of reality.
Public figure perfectly acceptable, they accepted this when they took a public job. Posting their home info etc would be improper.
XFS for starters it's the default nowadays on rhel/centos.
If your running a brand spanky new kernel, with data you do not care about why an old FS. Plenty of newer better FS's to choose from.
No one in tech does that.
Not true. In automotive space (what we are talking about here), repair of a 20 year old vehicle is quite common. In x86 space, modern software releases commonly apply to a decade old platform.
But the insinuation that Apple is a worst offender here is demonstrably false.
I wasn't implying that Apple was any worse than Google. However I do think such a perspective is a valid one on the x86 desktop platform side, where every other player except for Apple does a better job of supporting platforms over a longer time.
as far as the hardware itself will allow,
At the whim of Apple dropping support from some component of that hardware. In the handset business, no provider has proven that it could be easy to support older platforms so there might legitimately be too much churn in the platforms for that to be reasonable, but in the desktop space, the causes for Apple dropping support seem to be things that don't phase the other OS providers on that platform.
OTP is 1 bit encryption just a very strong 1 bit.
*Being* the infotainment system is not that great a play. Those systems are increasingly tied to the platform of the vehicle so you can't easily upgrade it without buying a new vehicle. Apple nor Google are particularly well known for being fond of supporting tech that, on average, would not receive a hardware upgrade for 11 years for any user.
Improving infotainment systems interaction with the driver's handset so that a handset upgrade drives all the value add they would want, that works. Hence Google and Apple doing their respective platforms, and car vendors looking to support both from a neutral platform rather than locking a very expensive vehicle to one platform or the other.
Large providers with a clue already use anycast for DNS. So assuming your ISP does a decent job peering you should never see a google DNS request going from NYC to Chicago outside of a failure of the DNS servers in NYC.
They propose shifting more latency sensitive bits to microwave links. Specifically DNS and TCP Handshakes ya know those top 2 DDOS vectors. We already have protocols to tunnel through DNS. I'm sure that will go so well.
Because their solution was powershell with it's own nonstandard remote interface.
The problem is they get sold a bill of good they never use. We have smartboard in every classroom, the actual smart portion of them is nearly never used. A projector and a screen would have sufficed just fine as that is what the use. Now the smartboard can easily cost 10x what the projector and screen does.
It's pretty much the same with anything technical, school see huge markups often when the bidding is limited to approved vendors for this or that matching grant.