Not true, the system still notices. The system gets calibrated when the tires are filled up by a competent driver initializing calibration through a simple 22 step process done entirely be a single button and a 2-line dashboard display. It's even written down in the manual that I'm sure every driver reads before operating a vehicle. The proper tire speed to engine speed is then stored in the computer over the next few miles of driving. After that point, any/all tire deflation will be noticed.

You list what permissions your app will need up front in the manifest. If your app then tries to do something that wasn't in that manifest, it won't be able to, because it doesn't have the permission. If Mr Malwharightar tries to be sneaky and omit a permission to make phone calls, then the code will not be able to make phone calls. I don't see the flaw.

Oh, I see. I stand corrected.

I came to my conclusion by making ill-founded assumptions and then using a single data point that appeared to back me up.

What a strange area to try to drive in.

There's actually nothing wrong with the route google shows there. First, you put the end point there, implying you actually want to get there. Second, there are parked cars in that street view, so apparently you can drive down that road for the purpose of parking (say, like when you tell google that your destination is on that street).

If you move the end point anywhere else, google routes you around that street. Ask it to take you to Oak St east of Octavia Blvd, and google takes you down Laguna St.

Doesn't the caching only apply to the single process ? It's not like you can have some background task running waiting for a sudo, or am mistaken there?

As an EE, I've had a couple jobs where I worked on weapons. In fact, I've worked on the Conventional Trident Modification program referenced by TFA. It can be a bit of a struggle to deal with the fact that you're building a weapon. There's one rational that got tossed around quite a bit:

The weapons will be built by someone. Would you really want the weapon design to fall only to engineers that couldn't get other jobs? Given that I worked on the guidance parts, I could be glad that I was involved in making sure the weapon only went where it was intended to go.

Granted, that first part is a bit of a strawman, but it's based in the reality that not all engineers will ever stop working on weapons.

In the past, I've also worked on a torpedo project. That was a bit easier since torpedos are rarely used against anything other than a naval vessel, especially the MK48. Missiles are definitely more taxing on moral. Also, the fact that you're working on a weapon was always present for me and affected every single design decision. I wish I could say the same seemed true for the management. I'm not sure how many times I said things like "We're building a damn missile here, how about we double check that?"