1

Topic: The infinite tape with the beginnings

(I notify at once - I not ) All of us we know sites with the infinite scrolling. This disgrace with  began, is then cunning to Tumblr and further everywhere. The user  page to a bottom, it from below , and so endlessly. Normally it is accompanied by absence of search in date and generally any search. Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. Whether do so though somewhere, and whether there is in it a sense generally? Whether the browser will release storage which has been selected under remote elements DOM, or final clearing of storage to happen only at tab/window closing?

2

Re: The infinite tape with the beginnings

Hello, Glory, you wrote: Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. Whether do so though somewhere, and whether there is in it a sense generally? Well if really brakes at users and if it helps why would be not present. I with such personally did not face, not absolutely clearly, about what speech. These are any feeble phones at which storage comes to an end or what? What should be page to gobble up all storage? To brake will be faster than that adding of new elements downwards causes recalculation of layout all pages and this process on feeble processors can reduce FPS. In general I first of all would try to understand, what exactly brakes. Whether> the browser will release storage which has been selected under remote elements DOM If links to them are not present, should.

3

Re: The infinite tape with the beginnings

Hello, vsb, you wrote: vsb> Well if really brakes at users and if it helps why would be not present. I with such personally did not face, not absolutely clearly, about what speech. These are any feeble phones at which storage comes to an end or what? What should be page to gobble up all storage? To brake will be faster than that adding of new elements downwards causes recalculation of layout all pages and this process on feeble processors can reduce FPS. In general I first of all would try to understand, what exactly brakes. At you is , it is possible (I hope). Open it, not on phone even, and on a desktop. Whether look through news or whose  page , scroll downwards, downwards, downwards. Brakes of begin that the browser   so many that conflicts to a disk cache. Earlier when browsers were in the core 32, 2 already were a limit for process. Now at me one browser Firefox is launched, it was arranged on 7 processes, they if in Far in the process list them to select - 5.3  occupy. Yes, and recalculation layout' - it obviously is not optimized under a large amount of elements. You after all remember, probably, such thing from  development - virtual grid when in the table on the screen were displayed ten thousand lines, but actually, they were not stored in a type of lines of that table-kontrola which is visible on the screen. The table was "a sliding window" over the present data, and it strongly accelerated interface operation, and even was generally a unique possible method to force it to display so a great number of elements.

4

Re: The infinite tape with the beginnings

Hello, Glory, you wrote: (I notify at once - I not ) All of us we know sites with the infinite scrolling. This disgrace with  began, is then cunning to Tumblr and further everywhere. The user  page to a bottom, it from below , and so endlessly. Normally it is accompanied by absence of search in date and generally any search. Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. Whether Do so though somewhere, and whether there is in it a sense generally? Whether the browser will release storage which has been selected under remote elements DOM, or final clearing of storage to happen only at tab/window closing? 1. Because the customer knows nothing about it, it puts the problem to the programmer, the programmer does. Yes brakes, but the task is fulfilled, the programmer received money, the customer the performed operation, all are happy except users. 2. Concerning browsers here a separate subject and a question for : what browser "leaks" more strongly? At me happened FF to the closed tabs to 1 ate off. The opera at idle time what for permanently starts to force a disk. Chrome I use rarely. 3. And at last a stone in ))) Imho in most cases in  go those who "" to become the normal programmer (I such therefore I know that I speak). Does not suffice them pore of knowledge of algorithms and structures, of optimization do not think absolutely. He should  be owned, instead of brains (I not such if that)

5

Re: The infinite tape with the beginnings

Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. What will be, when you will push home on the keypad?

6

Re: The infinite tape with the beginnings

Hello, Glory, you wrote: whether Do so though somewhere, and whether there is in it a sense generally? Whether the browser will release storage which has been selected under remote elements DOM, or final clearing of storage to happen only at tab/window closing? When it is necessary - do. At us in a product in  it is possible to load 100500 lines and to twist there-here. The amount of at a time displayed elements not such big also works quite tolerably.

7

Re: The infinite tape with the beginnings

Hello, koenig, you wrote: K> that will be, when you will push home on the keypad? To you show the beginning of a current tape. On a clique on an element "Above" begins  on top and cutting from below.

8

Re: The infinite tape with the beginnings

To You show the beginning of a current tape. On a clique on an element "Above" begins  on top and cutting from below. Oh . Well so it is to a certain extent normal, yes, but breaks intuition fully - at once to get to the beginning easier page to overload. I meant brakes at a jump somewhere upwards (about the same that at  from below in  and ). I at us somehow did such, but the content was strongly heavy (even background  did not rescue - simply insertion in dom and that the browser strained), it was necessary to leave paging.

9

Re: The infinite tape with the beginnings

Hello, Glory, you wrote: (I notify at once - I not ) All of us we know sites with the infinite scrolling. This disgrace with  began, is then cunning to Tumblr and further everywhere. The user  page to a bottom, it from below , and so endlessly. Normally it is accompanied by absence of search in date and generally any search. This "disgrace" reminds me  : something is invented well  high qualification, and for certain tasks, but becomes fashionable, becomes mass and inevitably it is possible in masses to the point of irrationality. To take, apparently, dear Ozon.ru. At them the necessary information is in  (about delivery, for example), and at the infinite page  paging, button "End" becomes stupid ... And it all brings down the infinite goods. It is possible to open, of course, other, short p. and to look, but after all delirium. I any more do not say that on storage loads not childly. On normal sites so does not become, certainly. Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. More likely on mind removal of objects of mute objects, and them "sliding reusage", i.e. when to the place of mute objects  the visible comes not. It can partially spare resources (and can not spare - it is necessary to investigate). Whether do so though somewhere, and whether there is in it a sense generally? Whether the browser will release storage which has been selected under remote elements DOM, or final clearing of storage to happen only at tab/window closing? I think, all is aggravated with that is a lot of browsers. Different engines with garbage collectors on different platforms can and work differently - nuances are possible. Well and versions are permanently updated. Today optimized, and in a year all starts to die. Better elementarily not to use the infinite p. there where really it is a lot of data. Or  alternative as, for example, in some  where simultaneously is both paging and the button " still", and all is convenient.

10

Re: The infinite tape with the beginnings

Hello, Glory, you wrote: (I notify at once - I not ) All of us we know sites with the infinite scrolling. An excellent question! Look towards game 2D (well or if absolutely it would be desirable mega a steepness 3D) In them this problem is solved initially, from a box, differently how to do ?! There the enormous game Universes  smoothly and imperceptibly also can be played (i.e. ) HOURS! It precisely is in gamemaker 2D, Phaser js and in others is simple if 2D the game engine of it is not able that it not game 2D an engine. Certainly it is in 3D -  and  And in the house there is a shadou-house probably sending in a shade that that above and below the screen somehow it is possible to master... But the ready decision from a box - like is not present, though did not search... By the way it is possible to look on  docs - there online easily  large tables

11

Re: The infinite tape with the beginnings

Hello, koenig, you wrote:> Sooner or later any similar page starts to brake, because elements in it becomes more than is capable to process in time an engine of the browser and any intermediate scripts on page. Attention, a question - and why anybody together with adding of elements in the end of page does not delete them from the beginning? That is, after defined the amount of "growths" of page, adding of each following element of a tape involves also removal of an element from the beginning. As a result, the page will have though also big, but nevertheless the finite size. K> that will be, when you will push home on the keypad? Nobody hinders to interpose into the beginning div in height 10050000px. At pushing home we spring upward and we start to create anew elements which get to a review window.