Unfortunately, not even that. They'll find an error in calculations, another doomsday theory or whatever....

Hit the nail.
If you have at least a little experience, you've already at least once gone through the codebase and asked who's the idiot that wrote that, checked the answer on the version control system to find that the idiot is yourself.
On the other hand, sometimes the legacy code is so much patched that it's easier and faster to rewrite it. If this code is that much patched that you can't even follow the code flow anymore, bugs left are only the scary ones anyway. Rewriting that code is a high risk task, since many errors already solved will be done again, but may still be worth it.

Li-ion batteries (laptop batteries) have really small changes in voltage output until very near the end of the charge. There's indeed a very precise integrator calculating the estimated remaining energy on the battery by measuring current and voltage.

No, redundancy means excess capacity.
Diversity means spreading the capacity through various locations/processes/etc. In this case we're talking about geographical diversity and the difference is simply distribution of the fabs around the world. If TSMC had its 15 factories spread over various locations, a single event couldn't shut down 100% of it's capacity.
The last year's earthquake in Japan shot down 1/3 of the Renesas fabs. It was enough to make a huge problem, stop some auto manufacturers, but it kept running. Had Renesas all it's fabs on North Japan, it would be 100% down. The fabs were not redundant, as one could not cover for the lack of other.

It's about diversity, no redundancy.
For semiconductor manufacturing, for example. There's quite a few plants around the world, not that much of small process nodes. If a major earthquake hits Taiwan, shutting down TSMC and UMC factories, you'll notice the effect all around the world pretty fast.
This http://eetimes.com/ContentEETimes/Images/120514_icInsights_micron_800.png should give an idea.

That's because there's no "sad but true" mod.

Having compiled the same code for ARM, x86 and x86-64, with the same compiler, I dare saying that the ARM code is much smaller.
Compiles using -Os and GCC for all cores.
Embedded has code size as a limiting factor for quite some time now...

P.S. before saying that a sample size of one isn't evidence, I develop firmware for ARM and some other arch e frequently compile it on the PC for testing purposes.

So far the problem only got worse, so all of these could very well be right on the supposition that it's now irreversible.

No, they are not.
Means for implementation by an expert should be provided. The C++ code would be just an example of implementation. Try coding a MPEG encoder in Lisp and see if you can patent it.

Indeed. Since FF4 I can't use online banking with FF. Now with FF5 Acrobat Reader locks and fails every now and then. Befor you put the fault at adobe, it doesn't on FF3 or IE. Basically FF is becoming useless for me very, very fast. And I'm the ordinary user. On the enterprise level here it's already forbidden.

I'd say you just confirmed my point. You don't have to surrender your right simply because the papers would be reversed then. Someone shouting that this or that genre of art is disgusting and should be forbidden is attacking a basic right (free speech) of someone else is just like someone shouting that organ donation should be compulsory is attacking a basic right (physical integrity or even your right to live).
Also, you can give someone the right to look for a job or happiness with no feasible way to achieve the goal.

Sure. Don't we kinda do that already, in economic terms? (poor people's work pays rich people's health care while having (almost) none themselves)

You may redefine the security of your own person to include quite a lot.

Very true... Suppose there's a hungry vampire just in front of you, about to die if not by your blood. Which right to live is bigger? (from a book I read a long time ago). Let's get a not so hypothetical and fantastic case, let's say you're in front of a severe renal patient and known to be a compatible donor. You don't want to live with a single kidney, which right is more important, his right to live or your right not to have your organs harvested?
You're always limiting the rights of other people, including their right to live, by asserting your rights. The problem is where to draw the line.

No, the problem is not money. The problem is bureaucracy, unwillingness to help and the arrogance, usually all present on TI departments.
Or simply things like:
ME: I need dotProject installed for use within my department. Could you deploy that? How should we proceed?
IT: dotProject isn't in the list of allowed softwares, MS Project is on the list, you should use it.
ME: 100 licenses of MS Project is too expensive, I need a simple service added to the linux box you already manage and have integrated with our domain.
IT: Sorry, you must use MS project.