The problem is that Twitter broke links to tweet pages by using the #! URL structure. Now you can't load a tweet page without loading the entire app. That's bad.
Too bad for IE users. They've said they're redoing it to given users of modern browsers the best experience, and if you use a crap browser you just get full page loads. /#!'s are getting kicked to the curb
Comments
The problem is that Twitter broke links to tweet pages by using the #! URL structure. Now you can't load a tweet page without loading the entire app. That's bad.
They'll move to pushState and all will be well. Hash-bang URLs were just a necessary stopgap solutions until more browsers supported pushState.
I would like to think so, but they haven't yet. They don't even load any page content, so that you don't get URLs like http://twitter.com/stuff/1234/things#!/different/stuff
No version of IE - not even IE9 - supports pushState. Nor does the Android browser, for that matter.
http://caniuse.com/history
Too bad for IE users. They've said they're redoing it to given users of modern browsers the best experience, and if you use a crap browser you just get full page loads. /#!'s are getting kicked to the curb
It's easy enough to use pushState where available and fall back on #!
Or just failover to full page refreshes, like we do at gdgt.
Not strictly true. IE10 supports it.
If you would like to think so, let me give you a reason to do so: http://www.2ality.com/2012/02/twitter-pushstate.html