Live data from Hacker News

Normalize v2.0.1 - optimized for modern browsers

necolas.github.com

1–10 of 15 posts

Re: Normalize v2.0.1 - optimized for modern browsers

#4

I don't get it, is everybody ready to drop IE7 support?

In certain segments: yes. If you're doing something aimed at developers or gamers, supporting IE (any version) isn't all that necessary.

I "dropped" IE8 support in 2010: http://impactjs.com/

Re: Normalize v2.0.1 - optimized for modern browsers

#5

I don't get it, is everybody ready to drop IE7 support?

Maybe not everybody, but it’s a reasonable default. IE8 has been out for more than three years, and works on Windows versions as far back as XP, which in turn has been out for more than a decade and is nearing the end of support from Microsoft.

There is accommodating customers, usually large organisations, who for whatever reason have chosen stability in their system software. And then there is not taking advantage of new technologies that almost everyone in most markets can use, and that almost everyone else could upgrade to if they needed to, just to support a tiny and shrinking minority.

Re: Normalize v2.0.1 - optimized for modern browsers

#7
post #3

I don't get it, is everybody ready to drop IE7 support?

If you don't need to support legacy browsers, then you can use 2.x. If you still need legacy browser support, then use 1.x.

Sorry, i did not make myself clear. It was more a general question. I was under the impression most webdevelopers still try to support IE7.

Re: Normalize v2.0.1 - optimized for modern browsers

#8
post #3

Earlier quoted context omitted.

If you don't need to support legacy browsers, then you can use 2.x. If you still need legacy browser support, then use 1.x.

Sorry, i did not make myself clear. It was more a general question. I was under the impression most webdevelopers still try to support IE7.

There are different values of "support". I "support" IE6 and 7 (I make sites for small businesses in the UK), as in, the site works, and the content is accessible. Those browsers make up 0.8% and 4.1% of the traffic last month respectively. (Why the hell is IE7 still used? How do people even have it installed???). For those, I'm happy to strip out sections if needed to get things to work, though this is rarely needed to be honest.

IE8 makes up 11.9%, so we do proper testing there, and the content should look as close as possible to modern browsers, but I'm happy to include polyfills etc where needed.

For us, Chrome is 21.1%, Mobile Safari is 17.5%, IE9 is 17.1%, and Firefox is 15.6%, so for us over 70% of users have a modern browser. These 4 are our target browsers, where everything should work.

Re: Normalize v2.0.1 - optimized for modern browsers

#9
I believe you had a sample/demo page with v1? I thought that highlighted what the stylesheet achieves quite nicely.

Also, I reckon test case examples for each browser quirk would be cool, so people who wanna see what each thing changes/causes, can go through the commented code and see what removing certain declarations would change/effect.

Keep developing cool stuff necolas!

Re: Normalize v2.0.1 - optimized for modern browsers

#10

Earlier quoted context omitted.

Sorry, i did not make myself clear. It was more a general question. I was under the impression most webdevelopers still try to support IE7.

There are different values of "support". I "support" IE6 and 7 (I make sites for small businesses in the UK), as in, the site works, and the content is accessible. Those browsers make up 0.8% and 4.1% of the traffic last month respectively. (Why the hell is IE7 still used? How do people even have it installed???). For those, I'm happy to strip out sections if needed to get things to work, though this is rarely needed…

Nice to see some actual data!!
Post reply on HN