Wait until your boss deletes that important document and your RAID system has deleted it on all drives in the array immediately at his request.

Or your business application is slowly corrupting the database and it is noticed (or finally confirmed) only after 3 weeks of use.

At that time you want to be able to get old data back. This is not something your array is going to be able to provide you.

Of course when someone had deleted half of the data in your finance database and you would notice it on the year or month close, you would already have overwritten all your backup media and lost your data forever.

Some time, someone will come at your desk and ask "I'm sure I had that contract in my documents folder last year but when I look now it has vanished".
At that moment you will realize that your backup rotation scheme is not as clever as you first believed.

I'm not sure how everyone gets so ecstatic about those cloud backups. When we would need to send all our data over the internet connection it would take an unworkable amount of time to complete the backup.
Even to the local LTO-4 drive, which runs at over a gigabit per second, the backup takes an appreciable amount of time.
Cloud backup may be good for a 3-man company doing document editing, but with the amounts of data that are common these days, and the speeds of internet connection that you normally have, I don't see it as a realistic possibility.

RAID is not a replacement for a backup.
RAID will safeguard you against the failure of a single disk (if and only if you monitor the system and replace disks as they fail), but backup will give you back your data as it was before your application destroyed it or your user deleted it. That is something completely different.

What people apparently don't realize is that there are way too many features in PDF to do a quick and dirty viewer.
It will probably work on some simple PDFs created by a "print to PDF" tool, but once you start viewing more advanced PDFs you will be in trouble.
Some time ago we switched from Adobe Reader to a competitor PDF reader where I work, and we still encounter PDFs that view OK in Adobe but fail in the new viewer.
Especially (but not only) PDFs that contain user fillable forms cause trouble.

The experience is much like using another browser than Internet Explorer was 5 years ago.
Often it worked, but frequently you encountered pages that won't render or function correctly.

Well, you have one very simplistic view of "backup"...
I would not talk about crusty old IT departments if I were you...

Probably the number of addresses in the utilized Internet that are intended to send mail is much lower than that 20-30%.

So it could still be a good method.

The thing is that it does not matter at all how secure the organization you buy your certificate from is.
What matters is how secure the lease secure of those hundreds of organizations that sell certificates is.
You can buy your certificate from the most secure one, but someone else can buy or steal it from the least secure organization and it will be trusted just as much.

To revoke the DigiNotar intermediate, a browser that has OCSP or CRL does not need an update. At least if it is formally revoked by Dutch state (which it isn't, AFAIK).

The updates are only required for root certificate revocations, apparently there is no OCSP or CRL for those (something that should be fixed).
But Mozilla is not distrusting the certificates based on revocation, but guided by the "CN=DigiNotar" in their issuer field.
That is why they need to upgrade the code.

In fact it is ugly, hardcoded exceptions for specific mishaps are being added to the software.
Something should be done that enables control of this kind of mishaps without having to update the software.

E.g. at work we have a Mozilla Seamonkey 2.0 deployment that I cannot yet upgrade to 2.3 because of bugs in that version and there are
no updates to 2.0 released anymore. Of course OCSP is enabled, but it would be better if it also worked for root certificates.

They should, but they haven't done that yet.
There is a security bulletin 2607712 that explains what they did for Vista and newer, but for XP and 2003 they should release a new version of rootsupd.exe that will update the list of root certificates.
This is not an update to IE but to a separate Windows component that stores the root certificates.