Twitter returns to server page generation
Twitter announced a new architecture change : the pages will now be generated on the server side, not on the client side.
After the last upgrade in September 2010, all UI rendering and logic was shifted to JavaScript on the client side. Browsers directly accessed the Twitter REST API, as did mobile clients. Although this approach has helped to realize a number of advantages, the developers have lost the optimization opportunities that are available with the server-oriented approach. As a result, users began to complain about the subjective “freezing” of twitter.com pages.
This week, a new architecture has been rolled out for static links (permalinks). As the tests showed, the page loading speed in the user's browser increased on average by five times, and the gap between different browsers, which cope with JavaScript in different ways, was significantly reduced.
Now, on top of the already generated pages, the user will download a new modular JavaScript application with a dependency tree for various interactive functions. The new framework will allow you to quickly add new features there, to adapt it for new technologies, the support of which appeared in browsers.
')
For permalinks, the new system is already working, and in the next few weeks it will roll over the rest of the site.
By the way, as you can see, hashbangs (#!) Disappeared from static links, this is one of the consequences of optimization. Some of the work on executing JavaScript, recognizing the path, downloading and rendering content for the specified URL was removed from the browser.
After the last upgrade in September 2010, all UI rendering and logic was shifted to JavaScript on the client side. Browsers directly accessed the Twitter REST API, as did mobile clients. Although this approach has helped to realize a number of advantages, the developers have lost the optimization opportunities that are available with the server-oriented approach. As a result, users began to complain about the subjective “freezing” of twitter.com pages.
This week, a new architecture has been rolled out for static links (permalinks). As the tests showed, the page loading speed in the user's browser increased on average by five times, and the gap between different browsers, which cope with JavaScript in different ways, was significantly reduced.
Now, on top of the already generated pages, the user will download a new modular JavaScript application with a dependency tree for various interactive functions. The new framework will allow you to quickly add new features there, to adapt it for new technologies, the support of which appeared in browsers.
')
For permalinks, the new system is already working, and in the next few weeks it will roll over the rest of the site.
By the way, as you can see, hashbangs (#!) Disappeared from static links, this is one of the consequences of optimization. Some of the work on executing JavaScript, recognizing the path, downloading and rendering content for the specified URL was removed from the browser.
Source: https://habr.com/ru/post/144964/
All Articles