The point of a website has long been what ever that website wants that point to be.
>>"oh shut up"
If you think a little past your own a e s t h e t i c bubble, you'll realize what the web has become. The most platform independent way to communicate applications using a mostly unified UI api (HTML5/CSS). >>21625
Personally I believe that it isn't inherently the technology that bloat, but rather, as is usually the culprit, inexperienced programmers that aren't keeping an eye on the UX. Some pretty horrific things are being done with JS (and CSS) in terms of performance. Very few webdevs will properly tune their website to be peformant across the average UX case. Pick and choose: either the webdev is too lazy to test their site across several browsers and platforms, or their is a distinct lack of education in this testing process to begin with.
I believe that it's a mixture of the two, but mostly the latter. Any casual glance at most of these code academy like tutorials or videos gloss over the bare necessities unless you specifically search for keywords like "performant JS", or "UI/UX tutorials". Which is probably why there are specific degrees and specific job titles pertaining to the UI/UX in particular.
This same effect happens in the realm of concurrency. Most desktop programmers (where concurrency/threads are available) fail to test the peformance of their software. And when they do attempt to add concurrency they run into problems such as using the proper conventions such as contexts, locks, semaphores, non-blocking I/O, polling, etc.
I'd say a more accurate description of things is Form = UI(function)
If we're thinking about closures.