The method that most frameworks and developers use to accomplish any form of "above the fold" reactivity, is to chunk portions of a page, where each of those ch

The method that most frameworks and developers use to accomplish any form of "above the fold" reactivity, is to chunk portions of a page, where each of those chunks gets its own renderer, of sorts, and whatever other dependencies that particular section of code might need. It's incredibly easy to either accidentally include large dependencies within each chunk, or repeat a dependency across multiple chunks, or to accept it as a problem to throw money at -- because it's far cheaper to expand infrastructure than to increase hiring, and way more palatable to the financial team when the buck just gets passed on to the consumer. For some reason, it has never really bothered project managers that just "throwing money at it" is entirely antithetical to the point of "above the fold."