DEV Community

Discussion on: is JS killing the web ?

Collapse
 
osde8info profile image
Clive Da

its any browser and any 20 tabs surely a Core i7 @ 2GHz with 8G ram should be able to do that in a fraction of a second ! why cant it ?

is max tabs quicker than ff or chromium tabs ?

Collapse
 
hackergaucho profile image
Hacker Gaucho • Edited

each browser works differently with the RAM memory and with JavaScript each page needs to be rendered asynchronously in real time.

I believe Firefox has more efficient processing in rendering the pages while Chrome/Chromium has better processing of videos.

there is some evidence that Google deliberately slowed YouTube on rival browsers, but that's another story.

the Max Tabs only limits the number of tabs open, which makes tab processing faster.

with the appearance of virtual DOM and the Web Components the processing ends up slowing down the number of asynchronous requests and the difficulty of optimizing browsers for all thousands of new libraries that use these technologies.

even with a top-of-the-line processor there is always a limit on the number of tabs that you will be able to open without generating a delay in rendering, there is no silver bullet.

for this reason I believe that the easiest way to avoid this is to find out the maximum number of tabs that your machine can process with high speed and use that number in an extension that limits the number of tabs open.

Thread Thread
 
osde8info profile image
Clive Da

nice idea but id like the reverse of this can someone tell me the spec reqd to open 20 tabs ? my experience that maybe only an i9 with 64G might be able to handle it