The business case for Firefox

Really smart explanation:

Giles Bowkett

The way to translate things for Joe Suit is to get him to do the math. Your initial expense to build the software is going to be X; your ongoing expense to add new features falls in the range of Y. However, if you’re asking us to develop Microsoft-specific code, your upfront costs will increase by alpha; and if you’re maintaining that code, your ongoing costs will increase by beta. Be honest, make alpha a lot but not too much, but beta is going to be huge. Firstly because any developer in their right mind hates Explorer, and should be compensated simply for even going near that toilet in the first place; second because bad design costs money. Maintaining for Firefox is simply less work than maintaining for Explorer. Less work means less cost.

And, yeah, I giggled at the toilet reference. I’m geek enough to admit that.

One last thought: Get Firefox.

Leave a Reply