In previous posts, I reported that upon upgrading from Office 2007 to Office 2010, corrupted some fonts caused Outlook and Word to crash. There are a couple of possibilities here. Maybe the fonts were fine before the upgrade, and somehow the upgrade corrected them. Maybe the fonts have been corrupted for a long time, and it wasn’t a problem for Office 2007, but is for Office 2010. The first alternative is extremely unlikely, since reinstalling the problem fonts doesn’t fix them.
It is clear, however, that the Helvetica and Times fonts installed on two computers (the only computers on which they are installed) cause Word 2010 to abend, and that Word 2007 was fine with them. This shows a clear lack of defensive programming on the part of the people who designed Word 2010.
There are two arguments against defensive programming. The first is based on performance: programmers argue that checking input variables and datasets causes the app to be pokey. The second is based on minimizing development time: putting in all of those checks and testing them doesn’t come for free. I don’t have a lot of sympathy with either argument; processing speed is getting pretty cheap, dataset testing is eminently parallelizable, and unreliable software puts users through hell.
I’m blaming this whole mess on the Microsoft programmers who let a little thing like an imperfect font crash their app (I used the word corrupted to describe the fonts before, but I think that probably overstates things, since the fonts worked in Office 2007).