In those articles, Yahoo stated that even using the meager percentage it found, that number corresponds to 20-40 million users across the internet. At 2009 census numbers, that’s the entire population of New York State on the low end or more than the entire population of California on the high end. That tiny percentage is no small number of users.
Gawker and Twitter
- Other policies at the destination may strip the file or block it in some way.
- A debugging console.log line accidentally left in the source will cause Gawker’s site to fail when the visitor’s browser doesn’t have the developer tools installed and enabled (Firefox, Safari, Internet Explorer)
I feel so strongly about how poorly Gawker implemented its new sites, about how Twitter relies on the same approach, how it all relies on a hack in Google’s spidering technology in order to even make it into the search engines, that you really do need to go read this post, to which I am linking again: Breaking the Web with hash-bangs
Updates: February 11, 2011
daring to live somewhere in the world where packet loss is a problem. I somehow suspect that Twitter users in Iran or Egypt might disagree that they dared to live there, or had a choice.
- Going Postel by Jeremy Keith.
- Broken Links by Tim Bray.
And for a little self-congratulation, this post was referenced in this week’s Web Design Update, something I have read for nearly its entire existence and hold with rather high regard. If you consider yourself a web developer and aren’t on this mailing list, you’re not really a web developer.
Updates: February 12, 2011
I found this script this morning which is designed to end the reliance on hash-bangs and the resultant URLs they force into page addresses: History.js.
History.js gracefully supports the HTML5 History/State APIs (pushState, replaceState, onPopState) in all browsers. […] For HTML5 browsers this means that you can modify the URL directly, without needing to use hashes anymore. […]
Updates: June 1, 2011
The post It’s About The Hashbangs points out that hash-bangs’ use as a stop-gap until
pushState is supported in browsers isn’t a valid reason to use them. He also addresses how hash-bangs break standard URL rules, confusing and confounding tried-and-true server-side processing methods. It’s worth a read.
Update: May 7, 2015
Which is why I sometimes stealth-surf using Lynx. It won't get tracked in Analytics and nowadays nobody looks at web logs anymore.
Darn, I was going to do this on a new site. I guess I will use VRML instead.
Sweet. I'll break out my copy of Netscape Navigator 4 with the appropriate plug-ins so I can slow my machine to a crawl.
[…] chart: http://kryogenix.org/code/browser/everyonehasjs.html I gathered links in my own old rants: https://adrianroselli.com/2011/02/beyond-hash-bangs-reliance-on.html […]
Leave a Comment or Response