Well, the difference between Firefox and Chrome is more than just the UI.

That is exactly what I am talking about.

This reminds me that I hate when Chromebooks use different firmware. Using different firmware for different OSes defeats the purpose of firmware standards like UEFI or ACPI.

To be honest this is not new. Remember the story of MS-DOS 3.1 for the DEC Rainbow?

Unfortunately, I think Server 2012 R2 is a paid upgrade unlike the client edition (Win8.1). And Exchange 2010 is not officially supported yet on R2.

I dug this out: https://mail.mozilla.org/piper...

What is funny is that the Morris worm came out in late 1988, when MS was beginning development on "NT OS/2". Yes, I am talking about the decision to use a flat instead of segmented address space.

Didn't know this. Looks like it is pretty limited though, as ACPI is much more complex than APM.

I think UEFI is the best solution for things like this and many firmware update utilities already uses it for example.

I don't think APM works on most modern machines though. There is the DOS idle utilities which execute the HLT instruction which is not much but is better than nothing.

Well, it is relatively cheap to do things like this during development of a new major version but relatively expensive to do a security update or hotfix, so they need proof there is actually an exploitable bug, though they will often review surrounding code and do additional fixes when developing security updates.