A Statistical Review of 1 Billion Web Pages
chrisd writes "As part of a recent examination of the most popular html authoring techniques, my colleague Ian Hickson parsed through a billion web pages from the Google repository to find out what are the most popular class names, elements, attributes, and related metadata. We decided that to publish this would be of significant utility to developers. It's also a fascinating look into how people create web pages. For instance one thing that surprised me was that the <title> is more popular than <br>. The graphs in the report require a browser with SVG and CSS support (like Firefox 1.5!). Enjoy!"
You get a decrease of the variance of the mean.
FYI, Opera also supports SVG. I'm surprised that Ian Hickson didn't have Opera also mentioned on that Google page, after all he worked at Opera until a few months ago.
Opera Watch - An Opera browser blog.
Because with statistics, increasing the sample size does not result in a uniform increase in accuracy.
If you start with a sample size of 1000 and add an additional 10000, the accuracy will increase dramatically. But if you start with 1,000,000,000, and increase it by another 1,000,000,000, the accuracy won't go up even by as much as 0.0001%
Yes, I'm pulling the numbers out of the air, but the point is that there exists a sweet spot where the additional effort does not pay off.
Your code usually goes like this:
So it is quite easy to get the empty table if the collection is empty.
No sig today.
Capitalization makes all the difference in the sentence:
i helped my uncle jack off a horse
"I'd rather be a lightning rod than a seismometer." -Ken Kesey
Try using a SVG compatible browser. SVG graphics *tend to* work better that way.
When the posters fear their moderators, there is tyranny; when the moderators fears the posters, there is liberty.
I don't believe Ian Hickson has been involved with Firefox; if I remember correctly, he used to hack on Mozilla, but then started work at Opera before Firefox took off.
I don't think it's a jab at Internet Explorer, it's just that he knows that the target audience is likely to have a decent browser, so he's used the features likely to be available.
Bogtha Bogtha Bogtha
Somewhat true. The HEAD tag is technically optional (per spec), but TITLE is required, and must be in the HEAD. Thus HEAD is required in practice.
From the HTML 4.01 spec:
Though marked as "start tag optional"/"end tag optional", the BODY and HTML tags do provide useful symantec relevance.
Image maps are often used on banner ads. I would guess that this is the main reason why they are so popular in this analysis.
http://www.adobe.com/svg/viewer/install/main.html got suitable plugins for browsers/OS of choice.
.ogg. Rootless promotion of this kind...
Notice that I got SVG plugin installed for ages, Safari didn't display the graphs. Is it because I am not using "a browser with CSS"? Well, nevermind really...
This is the thing why I and others have negative views against firefox, svg and even
The summary got it wrong,
the study states that there are more pages using title, than pages using br. NOT that more title tags are used than br tags.
Approximatly 98% of all pages have a title tag and approximatly 7 out of 8 pages have (at least one, probably more) br tags.
I have discovered a truly remarkable proof for my post which this sig is too small to contain.
If your Firefox 1.5 doesn't display the graphs, or crashes, do the following as suggested by the Google webstats author:
8 1#c3
Apparently there's a problem in Firefox 1.5 regarding SVG images if you
had SVG in the registry. Try following the steps described here:
https://bugzilla.mozilla.org/show_bug.cgi?id=3035
Yeah, I misspoke on this. Set-Cookie is insecure (due to domain-crossing problems -- should a cookie sent to a.b.c get sent to z.b.c? Depends on "b" and "c" in ways that depend on month-to-month political changes around the globe), but as far as I can tell, Set-Cookie2 is also insecure. I had thought it fixed this, but apparently not.
It has nothing to do with "cool"; SVG happens to be easier for us to produce than bitmaps, and anyone who is going to be able to read this report and view graphics will be using an SVG-capable browser. The fact that it found bugs in every SVG browser out there is merely a bonus, it means that SVG support will get better.
We used standards. It's not our fault if there was only one released browser that supported those standards well enough for you to be able to see the graphics.