Hamilton reported that once you've been through it a few times, then you know better how to implement the hacks. But, even with that skillset on tap, I asked Hamilton to give me an estimate of how many developer resources are squandered dealing with browser incompatibilities and he estimated 35 percent. 35 percent!! That's an amazing drain on developer resources if you ask me (one that's entirely resolvable). Could you imagine if, in any other business where there are supposedly standards, 35 percent of the industry's productivity simply disappeared down the incompatibility drain? Imagine for example, if telemarketing operators had to switch headgear on every phone call because calls to Verizon-based customers required different headgear than calls to QWest or AT&T-based customers. Or if truckers had to switch fuel systems everytime they crossed a state line. It would be unacceptable.
It's no wonder developers love runtimes like Adobe's Flash for developing rich Internet applications (RIAs). Developers can work with a single codebase works across all browsers and Adobe is a single throat to choke if it doesn't work. But in the case of IE vs. FireFox (not to mention Safari and Opera), there are four separate throats to go after.