that's true but if you separate the sources and cache them and return a "304 Not Modified" the modern browser will use the already cached resource.

as well as CDN can help you take away the load.

Something that some devs seam to miss -> the browser loads resources in a blocking way -> 1 MB js-lib is better than 14 small libs since 1 connection with cold start of the http protocol takes a while to get to full bandwith and does not block the rest of the app.

But that leads to far :) In the end all I want to say that SEO and modern Frameworks are not that easy to handle :)

the guys from karriere.at who do a lot of custom work, use a PHP library that uses the {{syntax}} so they can use the same template for different rendering (PHP/JS) engines. Which is a good attempt for more orthogonal usage of views :)

Yes it requires a different setup for public sites than backend systems. For backend systems I don't worry so much that the JS files is around 1mb since it's a limited amount of people using it and they just load it once and connections here in Denmark are in general 20mbit and above so it's a matter of seconds or less.

I think I will go for VanillaJS on my marketing pages then, because then I can keep it to less than 10kb. By time I will probably have my own cut down framework like I have my own components suite for backend more or less now.

I think that's a good Idea, it always annoys me that everything has to be in react or angular or [please enter arbitrary framework here]. if it behaves like a "page" and not a "component-container" why not render a page and add the 200-300 LOC vanilla JS, so specific components have a more dynamic look and feel.

It would be awful if a project just contains 4 files, instead of 200 modules from node so the 2 lines of code you want to run work gg ... dis-gust-ing ! :D