Live data from Hacker News

IE has 1% of market share ... on HN: "Show HN" aftermath

news.ycombinator.com

21–30 of 37 posts

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#22
post #3

It would be nice if the viewport size was included in stats like this as that is more important than screen size.

Agreed. I have a 2560px horizontal resolution but my browser is only around 1200px.

I ran some viewport stats on my own site a year back and found that for 95%+ the range was 980-1300px. I should run it again and come up with some more concrete numbers..

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#23
post #3

It would be nice if the viewport size was included in stats like this as that is more important than screen size.

It's not a standard feature for the Google Analytics tool but I found code that adds viewport logging:

http://beantin.se/post/354097397/track-viewport-google-analy...

http://wishfulcode.com/2011/11/02/measuring-viewport-size-wi...

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#24
post #20

Your calculation of claimed percentage of robots is deeply flawed. Not only do web browsers aggressively cache CSS files, but internet service providers also aggressively cache them. Though I'm a rare exception, my web browser is configured to ignore CSS completely, including both in-page styles and all additional loadable files. A configuration like this is very rare because it's difficult to do and the result often…

Same goes for JS files. There is only on page that I'm serving. I also know that there is 10% of visits are returning "customers". So there should be around 90 css/js files served per 100 html serves but it's not.

Few minutes after releasing the app on HN I saw a swarm of "...bot" user-agents in my logs and lots of 405 errors also for the "...bot" user-agents. That made me think that the disproportion might be cause by robots.

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#25
post #20

Your calculation of claimed percentage of robots is deeply flawed. Not only do web browsers aggressively cache CSS files, but internet service providers also aggressively cache them. Though I'm a rare exception, my web browser is configured to ignore CSS completely, including both in-page styles and all additional loadable files. A configuration like this is very rare because it's difficult to do and the result often…

[deleted]

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#26
post #20

Your calculation of claimed percentage of robots is deeply flawed. Not only do web browsers aggressively cache CSS files, but internet service providers also aggressively cache them. Though I'm a rare exception, my web browser is configured to ignore CSS completely, including both in-page styles and all additional loadable files. A configuration like this is very rare because it's difficult to do and the result often…

Some (most?) browsers cache based on the Last-Modified-Time of the resource, I know for example Mozilla does this (it will cache for ((now - mtime) * k), and I can't remember if k is 10 or 1/10).

Given that, is it possible your css has an older mtime then your "/"? If "/" is dynamically generated then the mtime will usually be set to now, whereas the css is often a file on disk with a real mtime.

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#27

Earlier quoted context omitted.

I imagine many HN visitors develop websites. Developing a website using IE or Safari would be a miserable experience.

Why would it be a bad experience to develop on Safari? It has extension support, a debug menu (which lets you change user agent) and the same web inspector as Chrome.

Agreed, anyone used to firebug will find Safari's Inspector very familiar. Even more so if they're used to Chrome's Inspector, which is not identical but seems like it shares 90% or more.

Re: IE has 1% of market share ... on HN: "Show HN" aftermath

#28

Earlier quoted context omitted.

I imagine many HN visitors develop websites. Developing a website using IE or Safari would be a miserable experience.

Why would it be a bad experience to develop on Safari? It has extension support, a debug menu (which lets you change user agent) and the same web inspector as Chrome.

It must have improved substantially. I remember having trouble finding out how to even activate a console, and then being blown back by how far behind Firefox+Firebug it was.
Post reply on HN