4 ms·

But IE6 isn't 70% of your userbase. Maybe 70% of your userbase is IE but only maybe 20-25% of that is IE6 so spending 30% more time/resources on IE6 is what I

But IE6 isn't 70% of your userbase. Maybe 70% of your userbase is IE but only maybe 20-25% of that is IE6 so spending 30% more time/resources on IE6 is what I would call a major fail. But hey, that's just me. And have you ever tried to develop complex ui sites on IE? I'm sorry...it just sucks and there is no good way around that. And I'm someone who knows IE6/7 quirks pretty good. Their script debuggers are utter crap and their developer toolbar is the most ancient thing out there. At least in IE8 they are copying Firebug...at that point it might not suck as much but who knows until I use it a while.

jasonkester 18y ago
Yes. I developed the most complex UI site I've ever seen, Twiddla, on IE first followed by Firefox. I never understood all the IE hate, to be honest. Until Chrome came out, I used IE7 as my daily browser. It's just better than Firefox in my opinion.
- sam_in_nyc 18y ago
  Voted up for developing Twiddla for IE. I share your sentiment.. I develop against IE first then test it against the "good" browsers... which rarely screw it up. IE sucks for script debugging.. I mean EPIC suck. You're not even told what line of what file is screwed up (IE seems to concatenate everything into 1 file when giving the error report), but I've learned to rely on myself not to make common scripting mistakes, and created a cross-browser "console" object to aid in debugging. Safari has the worst script debugging on the planet. It essentially tells you whether or not there was an error. Oh, wait... and how many errors, total. Thanks, Safari!
  - jasonkester 18y ago
    Get VS.NET, and suddenly IE has the best script debugging around. Firebug rocks and all, but VS.NET will drop you into a breakpoint will a full call stack, watch, step thru, etc. It's a proper debugger. And yeah, it takes about the same level of effort to develop against IE as it does against FF. The advantage is that your stuff generally then works right in Firefox first try.
  - rbritton 18y ago
    Um, Safari has a full Javascript debugger built in: http://developer.apple.com/internet/safari/faq.html#anchor14 http://developer.apple.com/internet/safari/faq.html#anchor14 (among other google results)
    - sam_in_nyc 18y ago
      Amazing.. I can do console.log(). And if there's an error (which the link provided conveniently has), I get to see the entire file which gave the error. So helpful... I now know which file to sprinkle console.log()s in. Furthermore, it doesn't work at all for dynamically loaded JS. But, then again, there apparently were several Google results.
- dcurtis 18y ago
  And somehow, you managed to cause a bug in Twiddla I have never seen elsewhere. When you make the window smaller, some of your content actually goes off the edge: http://dustincurtis.com/screenshots/Team_WhiteBoarding_with_Twiddla_-_Painless_Team_Collaboration_for_the_Web-20090303-234517.jpg http://dustincurtis.com/screenshots/Team_WhiteBoarding_with_...

jasonkester 18y ago

Yes. I developed the most complex UI site I've ever seen, Twiddla, on IE first followed by Firefox. I never understood all the IE hate, to be honest. Until Chrome came out, I used IE7 as my daily browser. It's just better than Firefox in my opinion.

sam_in_nyc 18y ago
Voted up for developing Twiddla for IE. I share your sentiment.. I develop against IE first then test it against the "good" browsers... which rarely screw it up. IE sucks for script debugging.. I mean EPIC suck. You're not even told what line of what file is screwed up (IE seems to concatenate everything into 1 file when giving the error report), but I've learned to rely on myself not to make common scripting mistakes, and created a cross-browser "console" object to aid in debugging. Safari has the worst script debugging on the planet. It essentially tells you whether or not there was an error. Oh, wait... and how many errors, total. Thanks, Safari!
- jasonkester 18y ago
  Get VS.NET, and suddenly IE has the best script debugging around. Firebug rocks and all, but VS.NET will drop you into a breakpoint will a full call stack, watch, step thru, etc. It's a proper debugger. And yeah, it takes about the same level of effort to develop against IE as it does against FF. The advantage is that your stuff generally then works right in Firefox first try.
- rbritton 18y ago
  Um, Safari has a full Javascript debugger built in: http://developer.apple.com/internet/safari/faq.html#anchor14 http://developer.apple.com/internet/safari/faq.html#anchor14 (among other google results)
  - sam_in_nyc 18y ago
    Amazing.. I can do console.log(). And if there's an error (which the link provided conveniently has), I get to see the entire file which gave the error. So helpful... I now know which file to sprinkle console.log()s in. Furthermore, it doesn't work at all for dynamically loaded JS. But, then again, there apparently were several Google results.
dcurtis 18y ago
And somehow, you managed to cause a bug in Twiddla I have never seen elsewhere. When you make the window smaller, some of your content actually goes off the edge: http://dustincurtis.com/screenshots/Team_WhiteBoarding_with_Twiddla_-_Painless_Team_Collaboration_for_the_Web-20090303-234517.jpg http://dustincurtis.com/screenshots/Team_WhiteBoarding_with_...