This endless live scrolling..
Dec. 14th, 2011 09:33 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ceagleYou know, the endless live-scrolling code that Twitter and Tumblr and a few other places are using now.... does anyone really like it much?
With every new increment, interaction with the page gets slower, and slowwwwwwer, and slowwwwwwwwwwwwer.... so this never-ending continuously loading more-and-more on the Same Page... seems like it's clunky and bothersome to me... I'd rather go to a "next page" in succession, like most pages/blogs are .... at least then you know there's a limit to the LOAD LAG ;P
With every new increment, interaction with the page gets slower, and slowwwwwwer, and slowwwwwwwwwwwwer.... so this never-ending continuously loading more-and-more on the Same Page... seems like it's clunky and bothersome to me... I'd rather go to a "next page" in succession, like most pages/blogs are .... at least then you know there's a limit to the LOAD LAG ;P
no subject
Date: 2011-12-15 05:54 pm (UTC)This is actually a Javascript hack that people have nicknamed "Comet." It works essentially by never finishing the page load -- the server keeps the connection open, and periodically pushes out a new Javascript code fragment that inserts a new <div> into the page with the new content, which the browser executes on the fly due to incremental rendering. The problem is this causes the page to grow forever; the browser never stops rendering it and each <div> tag adds to the size of the page.
The reason for this hack is HTTP has no built-in way to push data on demand from a server to a client; it can only pull data.