The other day, while trying to build a docker image from inside a VM running Ubuntu(temporary setup due to issues with getting a Docker Desktop license), I had

The other day, while trying to build a docker image from inside a VM running Ubuntu(temporary setup due to issues with getting a Docker Desktop license), I had a moment to pause and reflect on how no matter how fast hardware becomes, humanity always manages to make it slow. The reason for this is related to the way development of browser-based applications (be it Electron apps or just web apps) is scaled. In order to make 20+ people work on such a project effectively you need loose coupling, so the codebase is divided into those small, independent modules - each making its own API calls. And herein lies the crux of the issue. Chrome/Chromium/Electron etc. currently have a hard limit of 6 HTTP requests being processed at any given moment - the rest is queued(or "stalled"). Notice how weirdly slow is gmail to load? It's making a total of 200+ requests. No matter the network bandwidth that's going to take a while. Same goes for banking apps, or any kind of back office application. As usual, in order to make development faster they're making the app slower.