We don't support Internet Explorer, and we're calling that a feature
1–10 of 167 posts
Re: We don't support Internet Explorer, and we're calling that a feature
#2Sounds like a bunch of butt hurt emo nerds
Re: We don't support Internet Explorer, and we're calling that a feature
#3I didn't support IE until, much to my chagrin, I discovered about 30% of my hits were from IE. Fortunately, simply putting the !doctype meta-tag (or whatever it is) fixed almost all my issues (at least for IE 8+)
Re: We don't support Internet Explorer, and we're calling that a feature
#4I didn't support IE until, much to my chagrin, I discovered about 30% of my hits were from IE. Fortunately, simply putting the !doctype meta-tag (or whatever it is) fixed almost all my issues (at least for IE 8+)
Very wise. This post is by no means a prescription for everybody. We're lucky that our demographic tend to use stronger browsers. Actually, when I exclude blog traffic the IE percentage drops further. :)
Re: We don't support Internet Explorer, and we're calling that a feature
#5Ten years ago you were an elite web developer if your site worked well in browsers other than IE. Today you're an elite web developer if you can make your site work well even in IE.
Re: We don't support Internet Explorer, and we're calling that a feature
#6I never saw any app or website that would have a that low percentage of IE usage.
Anyway, if you have been working with html&css for more than 1 or 2 years it should not be hard to at least degrade gracefully on ie8+.
Personally I don't even think it is a choice, ie is still 30% of world average, supporting it is a must.
Re: We don't support Internet Explorer, and we're calling that a feature
#7This would have been interesting news in 2007 when ~70% of the internet was using IE and the versions that people used were hard to support. Now, it just seems like silly bragging. I can understand silently not supporting IE because of the features that aren't present, but shouting that you don't support IE in 2012 and calling it a feature just comes off as arrogant. My first reaction is, "so what?"
Re: We don't support Internet Explorer, and we're calling that a feature
#8Ten years ago you were an elite web developer if your site worked well in browsers other than IE. Today you're an elite web developer if you can make your site work well even in IE.
Getting the vast majority of sites working in IE9 is trivial (no changes required). IE8 some changes, but not a major hassle. I don't support IE7 or before. If you use a lot of HTML5 features it is hit or miss on all browsers.
Re: We don't support Internet Explorer, and we're calling that a feature
#9I never saw any app or website that would have a that low percentage of IE usage. Anyway, if you have been working with html&css for more than 1 or 2 years it should not be hard to at least degrade gracefully on ie8+. Personally I don't even think it is a choice, ie is still 30% of world average, supporting it is a must.
It really depends on the site though. I get almost zero IE traffic.
Re: We don't support Internet Explorer, and we're calling that a feature
#10Aw man. As a bootstrapping web business guy, I can say I've had way more problems with supporting iPads and iPhones than IE. IE costs me $0 to support, and I don't even bother (nobody asks!). Supporting hip and popular Apple browsers can run me a grand in a fast minute. Pleasing early adopters without working really well on the iPad3 is a tough sell.
I think startups fighting to support I'm not crazy about getting an iPad myself, but I'm starting to feel cornered into spending hundreds of $$ on one just to keep those early adopters happy. I think this is where the real browser/device compatibility discussion is, not around IE.