No more hashbangs! Twitter is moving rendering back from the browser to the server
What was revealed in a twitter discussion before is now official – twitter decided to move back the frontend rendering from the browser to the server again thus removing the hashbang (#!) in URLs. This is quite a big architectural change.
All done for performance reasons.
It’s all about the time to first tweet.
Removing the hashbang and doing the rendering on the server again apparently improved the initial page load time to 1/5!
I’m looking forward to see this new architecture being rolled out completely to see if the user experience will improve as promised.