If you want "view source" to be useful, you need to go back to coding with simplicity in mind.
The original post talks about viewing the source of the google homepage and getting an incomprehensible slurry. But why? What does that actually accomplish? The page is one text entry box, and 2 buttons, plus a graphic above it. There is ZERO excuse for it being over 47,000 characters (not counting all the other stuff it pulls in).
Let's not conflate _visual_ simplicity with functional simplicity because the google homepage is not simple as described. The image is not a simple image, it's either the logo or a doodle that gets updated on various days or times. The text box is a regular text box until one starts typing or clicks the mic icon to speak a search, then it changes to a predictive search and starts showing results to get users to where they want to go more quickly. The top bar is not just decoration, it's links to other google apps and a user/login widget.
But this isn't at all rare on today's web. This is also why so many pages are so horrendously slow to load, it's all scripts and links to other files and domains, even the simplest websites use absolutely incredible amounts of bandwidth, and yet do no more than could be done in 1/100th the size or less, and be human readable. 99.99999% of these sites aren't huge for any good reason, they're just horribly inefficient.
Since 99.9999% of websites cost money to build, maintain and serve to clients and since a majority of clients are interested in free content rather than paying for content, it's either selling product or services, showing ads or eating the cost to cover the cost of building and running the site. Ads are terrible and bloat out most web pages as they only care about the ad being shown and additional services require engagement from users. This results in annoying behavior for users as they've learned to ignore ads on pages or use ad blockers, so now it's an entitlement fight - but remember that content creators don't have to create content. :-)
As well, _most_ of the little sites (blogs, etc) use some sort of CMS framework to drive it and their owners want the blog to both look nice and have engagement features like sharing, etc., which requires more assets and more downloading than "simple" sites. Not only this, but users expect websites to work and look great on any device they fancy reading webpages on, so now there must be a bunch of responsive work and extra code to handle this kind of thing nicely. Generally that means developers will use a framework like boostrap or material design to accomplish it. This increases page bloat but is offset by better caching of the library if using a CDN correctly.
Going back to google.com, the reason there's so much code in a "simple" page is that the guts of most of the logic for displaying the page and its widgetry is now working from the web browser instead of the server. It cuts down on page reloading and speeds up how quickly they connect users with their search results. And Google's front page and searching are _not_ slow.
TL;DR google.com is not simple and there's no such thing as free - it always costs someone something.