3 ms·
The solution is very simple. Pricing. Give your client two prices: one with IE6 support, the other without. Give honest prices based on the genuine overhead of
by tcarnell 17y ago
The solution is very simple. Pricing.
Give your client two prices: one with IE6 support, the other without. Give honest prices based on the genuine overhead of working with IE 6.
If the client is willing to pay for IE6 support, fine, do the work you are being paid for. Let the cash decide the future of IE6
...but this is another example of developers making decisions that they should be making. For example, a software developer that decides to build a system with full database independance (hibernate for example) COULD be doing the right thing, but could simply be driving up project costs for requirements that never existed.
Developers - DONT make these decisions, price the options and ask the client.
- adriand 17y agoThe problem with this approach is that it opens up a good angle for your competitors to attack you on compatibility grounds. They can tell your client that they don't charge anything extra for IE6 compatibility, leaving you explaining that either they are charging them but that it's a hidden cost, or that their sites are so crappy and outdated that they work fine in IE6 from the get-go.