.
Show me a self-driving car that could navigate the snow-choked roads of Boston this winter.

I agree. When I asked if innovation in Windows was relevant, I was referring to innovation in the Windows OS itself, not the apps that run on it.

.
With Windows 10, it's like I'm getting a half-functional OS if I choose to have a local account and not to log in to Microsoft.

.
I'm sure you can find one horror story or two or three about any business out there, some of which may even be true and not planted by competitors. If you really "steer clear" of a business because of one bad review on the Internet, then you must not buy anything.... ;)

Here are a couple of reviews that use more than one data point:

Best domain name registrars

Five Best Domain Name Registrars

.
You need to be very careful when sifting through data that you are seeing actual causality, and not just a coincidence that has occurred.

Hertz said, "No current plans to do so." [emphasis mine]

.
There's nothing to say that plans to use the camera may appear later today, tomorrow, next week or next month. If Hertz had not intended to use the cameras, they simply would not have put them in the vehicles.

You should look at OpenNTPd. Much, much easier to configure.

.
The config file on one of my servers has one line in it, the name of the server pool to sync to. With that one line config file, OpenNTPd syncs to the servers in the pool and does not open any ports for listening.

You say OpenNTPd has been broken "for years", yet do not say why or how. -1 for your efforts.

.
For my needs, OpenNTPd has been an excellent replacement for NTPD. I do agree that NTPD has some features that are not present in OpenNTPd, but my usage does not require those more esoteric features. What I do need is the ability to sync my server clocks within a few milliseconds, OpenNTPd does that quite well. And OpenNTPd does have one major feature that NTPD has lacked of late - security.

You should try to keep up. :)

.
Hopefully the ntp.org software fades away.

However, the Network Time Protocol should live on in more secure and more easily maintained implementations (e.g., NTimed and OpenNTPd).

.
While audits are nice, what are the OpenSSL developers doing to change the development environment so that the new, [hopefully] improved versions don't revert to the security-challenged versions we've all come to know?

It's easy to change code, much less easy to change developer attitudes.