So if I understood this correctly, web "developers" pull in all these frameworks so that they would avoid writing common code. If the intent is to avoid writing

So if I understood this correctly, web "developers" pull in all these frameworks so that they would avoid writing common code. If the intent is to avoid writing common code and also to avoid pulling in bloat, wouldn't it be logical to turn the problem "upside down on its head" and identify what common code is actually required, and just write / isolate / pull that in? If all those pulls are made just for one to three trivial functions, to me that's not worth the bloat (and frustration). Lesson I learned from this article: when it's time to write the web portion of my application, write just the minimum of minimum of what I actually need in the GUI in JavaScript, and write as much as possible to run on the server. Don't use frameworks. Don't try to be fancy. Be as functional as possible while being as simple as possible (and no, that doesn't mean "use flat GUI look").