top | item 3538239

Developing for old browsers is (almost) a thing of the past

42 points| lancashire | 14 years ago |37signals.com

36 comments

order

AndrewDucker|14 years ago

By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet.

This leaves them with only one option if they want support on a long-term supported browser, which is the recently shipped Firefox Enterprise Support Release.

WildUtah|14 years ago

>>>By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet.

Nonsense.

Chrome and Firefox will both run on XP.

helipad|14 years ago

Except there are no customers. It's a new product, and if you want to use it then you'll need an up to date browser. No-one is being cut off.

melling|14 years ago

Sounds like they simply want to remove as much legacy as possible in the new product. The old product will still work. They are "skating to where the the puck is going to be..." in a year or so.

billpatrianakos|14 years ago

It's totally necessary though. Developer's can't be supporting old browsers forever. And really, when we speak of "old browsers" we really just mean IE which still throws weird behaviors at you in the latest versions! When enough sites stop supporting these dinosaurs we not only give users a better experience on our sites but across the entire web.

Corporate customers can always use Chrome or Firefox on XP and if they can't then there's still Basecamp Classic for them. I think they're doing the right thing. It's a calculated risk and I think the odds are in their favor.

batista|14 years ago

By moving to IE9 he's discounting all corporate customers who haven't moved to Windows 7 yet.

Better framed: he's discounting all the corporate customers who drag their feet technology wise, and will give him more headache than money.

Such corporate late adopters are not usually the ones to use something external, much less Basecamp, anyway.

huskyr|14 years ago

I think the title is a little bit misleading. The moment you can drop support for browser versions is pretty dependent on the requirements of your client, and your visitors. 7% for users with IE8 or lower is a pretty tech-savvy crowd, many developers might not have the luxury of dropping support for IE8 because many of their visitors still use that browser.

eropple|14 years ago

Agreed. There's still a very significant portion of China using IE6, for example. If you've got an international focus on non-developers, it's not really even close to feasible to drop IE6-7.

mrspandex|14 years ago

I'm so sick of websites not even attempting to render in a browser not in their whitelist. Please give me a button that says "I understand the risks, but I want to try anyway."

dhh|14 years ago

We don't do that. We only discriminate against browsers we know will have problems. Like IE6-8. So what we're running is actually a blacklist.

If you show up with a browser that's not one of the big four, we're just letting you in on your own accord.

I completely agree that whitelisting for browsers is bullshit.

rmc|14 years ago

Some people don't understand the risks, but have been trained to click the OK button. They will then complain when the site doesn't work and completly forget that they clicked the "i accept the risks button"

hodder|14 years ago

The multibillion dollar organization I work for just updated to IE8 from IE6 last week. We aren't allowed to use new browsers or chrome frame for "security" reasons. ha!

randlet|14 years ago

Lucky you! I work at a large hospital with (likely) 10k+ computers running XP and we're still stuck on IE6.

I'm not sure what the plan to migrate away from IE6 is but my guess is that it will be a massive pain for our IT department.

I have to imagine that IE6 will continue to limp along for a number of years to come, but hopefully large organizations will have learned a lesson about depending on a specific browser version (or a specific browser for that matter).

johnbender|14 years ago

My understanding is that IE has a significant market share among users with accessibiliy needs (came up in conversation after the recent jquery 2.0 browser support discussion). While that may not be important for 37 signals it's an oft overlooked side effect of dropping version 8 support.

badmonkey0001|14 years ago

Now the problem becomes mobile browsers... (hover vs. tap, tiny resolutions, differences in form controls, sometimes crippled features that work fine in a "pc" based browser, fluid layout choices, float issues)

There will always be madness.

[edit] Took me a few to find this link again. Do compatibility charts like this look familiar? http://www.quirksmode.org/m/css.html

kenrik|14 years ago

IE6 may ye rest in peace... (or hell)