[mortenjorck]

A more accurate title might be "The Twitter web client is 2.0 MB."

[aaronpk]

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.

[marknutter]

They'll move to pushState and all will be well. Hash-bang URLs were just a necessary stopgap solutions until more browsers supported pushState.

[TazeTSchnitzel]

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

[icebraining]

No version of IE - not even IE9 - supports pushState. Nor does the Android browser, for that matter.

http://caniuse.com/history

[lparry]

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

[udp]

It's easy enough to use pushState where available and fall back on #!

[jonursenbach]

Or just failover to full page refreshes, like we do at gdgt.

[TazeTSchnitzel]

Not strictly true. IE10 supports it.

[pstjean]

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