Things may have changed since October 1st, but on second page load of the home-page, I'm seeing the majority of content as either cached or served by CDN, a relatively small functional payload compared to a lot of HN darlings, and an 79ms latency for the main request.
None of that is really alarming IMO.
Even so, half these assets are trackers and 3rd party resources that would probably be CDNed externally. If storage IO and bandwidth isn't your limit (and internally the URLs could easily be routed to different servers entirely as well as caching proxies), then it's pretty plausible that there's practically nil overall performance impact as far as service availability goes.
Also, I think the whole "you should only use one of each type of asset" philosophy is debatable at least.
"One obvious reason is that they're serving unminified and unconcatenated Javascript and CSS files. A single page load causes 92 requests to the server, and they're not using a CDN for any of that.
They're also not setting the Cache-Control and Expires headers, so the browser isn't caching many of those files, including on 80k file full of response strings.
For the non-technical, this means the site is essentially killing itself. An optimized and properly tuned production website would load one (1) HTML document, one (1) CSS document, and one (1!) JS document, they're loading 92. "