I’ve just learned something the hard way. There’s stuff out there that spins console.clear() and debugger in infinite loops. I don’t know why that’s a thing but I like to call it: clear console log debugger abuse.

In Chrome/Chromium limit debuggers and logs. In Firefox, enable log persistence/timestamps and control breakpoints manually.

My brain was picked apart the other day. Virtual scrolling is, in a handwavy sense, pagination with (semi) automatic navigation. Touché.

Infinite scrolling is unusual. Most implementations are “almost infinite” to avoid excessive DOM length (memory).

• Infinite scrolling: Limits content to an arbitrarily large amount to avoid exhausting memory.

• Virtual scrolling: Unload everything except the visible viewport + a top and bottom offset. Pad the rest.

Virtual scrolling is infinite, but breaks auxiliary actions ( CTRL + F ) because what’s on the screen is the content.

document.addEventListener("scroll", function() {
  console.log(document.querySelectorAll('*').length)
});

The most popular library appears to be https://infinite-scroll.com.

It’s amazing how trends in modern mainstream web development have seemingly inverted. One such example (an old bookmark) while following tech more closely in school;

Therefore by purposefully giving the user a blank page, we are giving him information that the app is still loading. The user knows that the app will be functional when he sees boxes and buttons.

The truth was it didn’t matter, at least, not so much as “position independent code”, kind of. Tech appears to do a ten year amnesiac/discovery routine. Web components arrived around that time too.