It's also about people like nurses that travel to visit patients in their homes, who are being paid a salary for the hours they work, but in some cases not for the hours spent travelling to the first patient and from the last patient. If the company is not paying for the time spent travelling to the first job and from the last, there's no incentive to optimise the routes so they start/finish close to home.

Relatedly, I believe the reason that Word is being used as the exploit vector on Windows is because it doesn't have the sandboxing of IE/Firefox/Chrome. While you could get a lot more people to run the Windows attack code if you posted it on websites, it doesn't do any good when every popular browser newer than IE6 is locked down to not be able to launch arbitrary programs or write to most of the filesystem or registry.

Actually from Office 2010 onwards it does have a sandboxed mode which is triggered based on the origin of the document:
http://blogs.technet.com/b/office2010/archive/2009/08/13/protected-view-in-office-2010.aspx

Incidentally I'm not sure Firefox has a sandbox as such at least on Windows - e.g. it doesn't run as a low integrity process like IE.

I expect the type of crash and outcome is quite different between those cases. A distracted/texting driver is probably more likely to end up going full speed into who/whatever they hit without even any attempt to take evasive action, because they're distracted in the first place.

I'd expect in general the turn signal crashes are much less severe, e.g. one car running into the back of another when the first one slowed to turn off without signalling, even if their might be more of these type of accidents.

I don't want to have to install a stupid unlocker program like I do on Windows.

Using such a program has a very good chance of causing random file corruption:

http://technet.microsoft.com/en-us/magazine/2009.04.windowsconfidential.aspx

"Forcing a handle closed is equivalent to reaching into a program and freeing some memory. The program thinks the handle (or memory) is still valid and will continue to use it. But since the handle is really free, it will be reused for something else."

Haven't they already taken the first step with compulsory driver signing in their 64-bit OSes?

IIRC, one of the reasons for requiring driver signing was not for the logo certification part (which I thought remained optional, but I may be wrong on that) but actually to help with Microsoft's crash analysis efforts.

With a signed driver it's much easier to identify the vendor of a buggy driver, get in contact and ask them to fix their code, and even offer to push out an update via the Microsoft Update tool.