When the phone is in the docking station/holder in my car, a finger print sensor on the back side is pretty much useless.
So I'll stick with the 7 until Samsung figures out a way.

Is it so hard to write code that compiles with 0 errors and 0 warnings that will pass valgrind with with 0 warnings?

Firefox (and by extension Tor) need to figure out why with 70+ threads they still have deadlocks. Perhaps they need a language that doesn't do threading?

Actually I exaggerated, currently Firefox is only using 68 threads to display this page...

Project without a _REAL_ system engineer?

Assuming of course the sensors are in the right place.
Bottom line, I still have my old Samsung Note 7 (pre-recall) because 1) I don't believe they solved the problem and 2) The old phone has a software limit on charging speed.

I suspect the real solution will be the Note 8

Make the police get them first!

Simple, make a law that all firearms involved in domestic policing (FBI, local police, various SWAT teams) must have the smart gun technology.

What's good for the goose...

Planes had to have a significant range - even drop fuel tanks had to be planned for (complicated plumbing + extra drag/weight at takeoff).
Need to carry significant armament - like a few 30ish calibre machine guns (7.62 mm). By the end of the war the US was pretty much .50 caliber only - and 6 to 8 of those in a plane - that is a lot of weight. The ME262 had 4 20 mm guns/cannons. Are you going to shoot through the props? if not, then you needed wing mounted guns. If so, you needed mechanism to keep from shooting the prop off the plane OR an engine/gearbox that allowed shooting through the tip of the propeller.
Finally, naturally aspirated engines might make for a good low level racer, but at 30,000ft, you need turbo or supercharging to keep things alive. More weight, more cooling

Its actually lack of fuel. Since the US Air force is no longer flying high compression/ high powered piston engine planes, the availability of proper fuel is extremely limited. Leaded fuel plus toluene (I think).

So drop State Farm.

20 years ago, Mustang 5.0 (1990 model) Erie insurance was 1/2 for a plain 5.0 vs. a GT. The GT had the extra spoilers (OK, higher repair cost), but more imporantly, the actuaries figured out that GTs were more likely to be involved in an at-fault accident. I let you ponder why (crazier drivers like spoilers?).
Anyway, for a $13000 car, State Farm wanted $4000/yr and Erie wanted $1100. Keeping in mind that at the time a 200hp 5.0 was considered a wild performance car.

Stability control often interferes with certain maneuvers - especially those that go beyond a tires ability to grip. In particular sliding or spinning the wheels. Stability control has gotten better as algorithms improve, but generally speaking, a professional driver can get a car around a track faster with stability control turned off.

Autonomous cars will more than likely drive at exactly the speed limit. So on that stretch of highway you were used to doing 65mph in a 55 zone... well that slow car (hopefully in the right lane) will be the Google one.

I guess that's when the human takes over?

You mean there is something outside the lab?

If you have a real stick shift transmission, not only is the stick actually connected to something (the transmission) but you would also have a clutch. Now clutch releases can and do fail, and at full throttle you would not be able to get the stick out of gear (unless you hit the rev limiter). Under load (like during acceleration) many/most manual transmission cannot be taken out of gear without taking the load off. I have driving a semi-clutch less transmission that allowed me to engage gears without using a clutch - but it needed a spark interrupter to get out of whatever gear it was in.

The prius did have an issue with anti-lock brakes. Essentially you hit the brake after going over rough pavement and the brakes would start pulsating (and not stop the car). This was due in part to software they used to transition from regenerative braking to normal hydraulic braking. It lengthened stopping distances, but didn't prevent the car from stopping.

As for Toyota, as far as I know, not a single crash had been attributed to Toyota. Maybe carmats.

Which is because a vast majority of these 'incidents' are utter BS.

Driver claims total brake failure yet later when examined by technicians, the brake seem to be working fine. Since brakes are an independant system - typically dual/redundant systems - how exactly do they magically completely fail then magically return to normal functions.

More likely the unintended acceleration is from hitting the wrong pedal (or in this case control) or simply coming up with a lie to justify getting caught speeding.

One big negative on C#. Your code ends up looking like Visual Basic.
You end up with single files with massive amounts of code. I've seen C# files with thousands of lines of code. Each button, each rule for the button etc. and they are not grouped by any rhyme or reason. The are simply tacked on the bottom as the next function. Thankfully Visual studio helps you find everything.

Makes code walk throughs either hit or miss (did we go through all the functions on that button?) or scatter brained (function 1 - start button, function 2 - dialog box, funtion 3 - menu item).