Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Choosing not to develop for IE makes perfect sense if you're building an app. Here's my own little anecdote:

In the last 4 months or so I've written around 10k loc for a JS app. and probably 3x that many lines of combines CSS and HTML. Number of hours troubleshooting differences between Firefox and Chrome? I'd say about 8. So one developer day's worth of work to sort out some minor issues with vendor prefixed css. I've gotten to the point now that I routinely go days without testing in FF, and when I do fire it up.... everything just works.

My estimate that supporting ie6+ would have put my progress back by about 2 months. On top of that is the ongoing technical debt of continuing to support IE.

I don't want to say goodbye to potential IE customers and that's where Chromeframe comes into play. Chrome frame is AMAZING. Takes about 60s to install. Allows you to create your own install procedure i.e Your_Site -> Install_Chromeframe -> Your_Site. Doesn't require a browser restart and no admin rights needed. Wow.

Of course if you're just building a regular website then sure suck up the few hours it takes to make it work in IE and bill 2x for the trouble.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: