- Reading a gazillion articles on hashbang URLs (#!). 99% of them seem to be over-emotionalized FUD.
http://twitter.com/timhaines/status/171676057357926401
— Tim Haines (@timhaines)Mon, Feb 20 2012 19:22:16 - @timhaines read mine. It's all facts. danwebb.net
http://twitter.com/danwrong/status/171680307404218368
— Dan Webb (@danwrong)Mon, Feb 20 2012 19:39:09 - The null was actually a link to his blog post, but Storify or Twitter has broken that. Here's the post: http://danwebb.net/2011/5/28/it-is-about-the-hashbangs …
- @timhaines plus, now I'm in charge of undoing twitters hashbang URLs I can confirm that all the issues in that article are very real.
http://twitter.com/danwrong/status/171680703824662528
— Dan Webb (@danwrong)Mon, Feb 20 2012 19:40:44 - @danwrong x months from now (when your project completes) Twitter will no longer use hashbangs?
http://twitter.com/timhaines/status/171680932191932418
— Tim Haines (@timhaines)Mon, Feb 20 2012 19:41:38 - @timhaines correct. All gone. It was a mistake for several reasons. PushState or bust.
http://twitter.com/danwrong/status/171681426297729025
— Dan Webb (@danwrong)Mon, Feb 20 2012 19:43:36 - @danwrong You're going to revert to page refreshes if the browser doesn't support PushState? Adding PushState support progressively?
http://twitter.com/timhaines/status/171682264722321409
— Tim Haines (@timhaines)Mon, Feb 20 2012 19:46:56 - @timhaines although I'm not sure why everyone is so adverse to page refreshes these days. You can make them fast too.
http://twitter.com/danwrong/status/171682857910157312
— Dan Webb (@danwrong)Mon, Feb 20 2012 19:49:17


