Live data from Hacker News

I don't know how to IE6

blog.colbyrabideau.com

131–140 of 165 posts

Re: I don't know how to IE6

#131

Earlier quoted context omitted.

http://blog.colbyrabideau.com/archive -- August 2011 Edit: OP is the poster of the blog also

>OP is the poster of the blog also Cool, welcome to HN, Colby. It's a good first submission, have you been lurking long? Why not join the conversation?

Probably because he's being torn a new one further up the thread. Welcome to HN.

Re: I don't know how to IE6

#132
post #116

Earlier quoted context omitted.

Ok, how about considering a different demographic: China. IE6 remains by far the most popular desktop web browser in China (Statcounter [1] says 50% of the market). If my site is targetting a Chinese audience, IE6 support is a must and no amount of persuasion will move the entire Chinese market to Chrome in a hurry. [1] http://gs.statcounter.com/#browser_version-CN-monthly-201007...

Another strawman. People using pirated OS's and being technically unsophisticated to the degree of being satisfied with what IE6 has to offer are extremely unlikely to buy your service or to provide any significant value to your advertisers. Basically they are leeches that will use whatever is cheapest/most convenient to them. Thus not having them as your user will only spare you some resources. But if they really wa…

People in those areas using IE6 do pay for services. I know. We were debating this very question, and decided to look at our paid users browser choices, and IE6 was, while not the majority, not the least of our concerns, either. Furthermore, the net loss of loosing IE6 users would have been the salary of a number of people.

Finally, we can support IE6 without losing out on the benefits of newer browsers.

Arguing for or against IE6 using made up fanciful arguments (people using IE6 aren't going to buy your product) is silly. Look at your own numbers. If your first suggestion isn't that, you're ignorant of the realities of web development.

Re: I don't know how to IE6

#134

This is immaturely and badly argued. So it took a massive two days for an intern to add IE6 support to a web app. This is actually a good argument for keeping IE6 support for the several percent of users who still have it. I am not saying there aren't good arguments for dropping IE6, but this just isn't it. Some of the supporting arguments are even worse - does he really expect a course called "Legacy Browser Support…

This is off to the side of IE6, but I think we make a big mistake when we calculate costs that way.

It isn't simply a question of whether immediate revenue is greater than 2 days of an intern. The question is whether the projected revenue is greater than the support costs of that feature over time and the opportunity cost, i.e. "we can't do feature X easily because feature Y is in there." The fact that people don't calculate costs that way in software development puts many organizations in a pickle.

Re: I don't know how to IE6

#135
post #15

2% of the US uses IE6. Explain that to your boss and ask if it's still necessary to support it. [Update] For Google Apps, Google no longer supports IE7. YouTube support for IE6 was dropped a year ago, and they make a lot of ad money from YouTube now.

If 50% of your customers are among that 2%, IE6 matters.

If you're a social media startup, the customers looking for social media solutions are probably also the folks who are NOT running IE6.

Re: I don't know how to IE6

#136
post #15

2% of the US uses IE6. Explain that to your boss and ask if it's still necessary to support it. [Update] For Google Apps, Google no longer supports IE7. YouTube support for IE6 was dropped a year ago, and they make a lot of ad money from YouTube now.

There was story floating around here not too long ago that had IE 6 at around 4%. Incidentally, Safari was around 4%. I know a lot of devs that want to make sure things look great in Safari but don't care about IE 6 at all. Granted the obvious argument is that 4% of Safari users is a large percentage of Mac users, but it just goes to show how deceiving browser share numbers can be.

I'd also posit that while 2% may seem like nothing for a site with a small flow of traffic, it equates to a lot of money for a high volume consumer-oriented site. I run into a lot of this through my affiliation with Mogotest. During our customer development process I was amazed to find that several of the CTOs I sat down with will support any browser with greater than 0.5% share on their site. And these are guys that have definitely done their cost/benefit analysis.

Re: I don't know how to IE6

#137
If having the site IE6 compatible brings in more revenue then whatever they pay you for two days work, then it sounds like a pretty solid investment.

Re: I don't know how to IE6

#138
post #102
post #45

Earlier quoted context omitted.

I seriously doubt IE6 support can be the difference between "wildly profitable and failing" for any business. Can you name one example of a failing company that started supporting IE6 and then became wildly profitable?

Maybe not in 2011. But a couple years ago, it wasn't unusual to see 50% IE6 traffic on corporate-oriented apps. And, yes, I can give a few examples were the webdevs ignored legacy browser support and got burned.

I'm genuinely curious to hear which web developers ignored legacy browser support and got burned. Please divulge.

Re: I don't know how to IE6

#139
The fact of the matter is, this kid will be dealing with legacy type issues over the next 40-45 years of his career. 10 years from now, devs will be grumbling about supporting some technology we view as common place and whiz-bang today.

Yes, supporting IE6 is a pain in the ass (I have to do it due to my company's huge Chinese user base). But I am watching it die a slow death.

The specific experience sucks, but in general it will help him prepare for realities of web dev.

Re: I don't know how to IE6

#140
IE is the bane of my existence. It's got a lot easier over the last few years. The original turn from table based design to CSS back in 2005 was hell. It was guaranteed that half of your CSS would NOT work. It's a lot easier now but I still find some really weird issues.

Nowadays I use mogotest.com to help me with it. It's a lot more handy than booting up a VM.

Post reply on HN