互联网与文化pxlnv.com
废话连篇的 Web
The Bullshit Web
2018 — 2022，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这篇 2018 年的经典文章《The Bullshit Web》抨击了现代网页的臃肿：追踪脚本、广告、巨型字体和框架让一个简单的文章页面动辄几 MB，加载缓慢且充满干扰。作者认为这些“废话”对读者毫无价值，呼吁回归轻量、快速、以内容为中心的网页。文章在 2022 年再次登上 Hacker News 首页，说明问题至今未解。
为什么经久不衰：网页臃肿问题多年未改善，这篇文章对“现代 Web 为何越来越慢”的诊断至今仍然成立，是讨论 Web 性能与广告经济的常读经典。
HN 评论精选
用《白鲸》字节数对比，直观展示新闻网站的数据浪费有多惊人
《白鲸》纯文本只有 1.2MB，而《纽约时报》首页要 6.6MB。读一篇文章要下载相当于十本《白鲸》的数据量，只为阅读 72KB 的正文。即使不考虑环保，这种低效也令人发指。
cheezymoogle查看英文原文
I've said this before, but it bears repeating: Moby Dick is 1.2mb uncompressed in plain-text. That's lower than the "average" news website by quite a bit--I just loaded the New York Times front page. It was 6.6mb. that's more than 5 copies of Moby Dick, solely for a gateway to the actual content that I want. A secondary reload was only 5mb. I then opened a random article. The article itself was about 1,400 words long, but the page was 5.9mb. That's about 4kb per word without including the gateway (which is required if you're not using social media). Including the gateway, that's about 8kb per word, which is actually about the size of the actual content of the article itself. So all told, to read just one article from the New York Times, I had to download the equivalent of ten copies of Moby Dick. That's about 4,600 pages. That's approaching the entirety of George R.R. Martin's A Song of Ice and Fire, without appendices. If I check the NY Times just 4 times a day and read three articles each time, I'm downloading 100mb worth of stuff (83 Moby-Dicks) to read 72kb worth of plaintext. Even ignoring first-principles ecological conservatism, that's just insanely inefficient and wasteful, regardless of how inexpensive bandwidth and computing power are in the west. EDIT: I wrote a longer write-up on this a while ago on a personal blog, but don't want it to be hugged to death: http://txti.es/theneedforplaintext
反方观点：臃肿可能是商业上理性选择，而非愚蠢
也许这些“废话”只对懂技术的极客来说是废话。也许企业尝试过纯文本方案，结果加上字体、样式表和脚本后业务反而变好了。也许做这些决策的人不是傻瓜，甚至比你更懂技术。
ukulele查看英文原文
Unpopular opinion alert: Maybe the "bullshit" is only bullshit to you, the thorny tech-savvy reader. Maybe businesses have tried the plaintext approach, and their business was improved by adding fonts, stylesheets, API calls, spinners, scripts, high-res images, and god knows what else. Maybe speed improvements are not important beyond a certain point. Maybe 5MB doesn't matter to most people. Maybe micro-optimization is costly in large organizations. Maybe other people making these decisions aren't idiots, and maybe, just maybe, they're even thornier and tech-savvier than you.
主张浏览器应提供流量上限机制，把选择权还给用户
Web 的计费模式荒谬透顶：你按用量付费（流量套餐、强制广告），却无法预知成本，甚至不知道内容能否正常显示。浏览器应该有可执行的硬性数据上限，由用户主动信任后才允许站点多用流量。
makecheck查看英文原文
We have a ridiculously-backwards model on the web where you essentially pay for what you use (via your data plan, and via forced ads prior to promised content) without having any way to know in advance what it will end up costing you to display content. Heck, you don’t even know if the content will display correctly after all that loading. Worse, there are many ways to trigger loads accidentally, meaning you may want none of the content but you end up paying for it through your data plan. We desperately need absolute maximums enforceable in the browser, reversing the firehose. I want to opt your site in to more data use, after I trust your site. And I expect sites to work within my limit or not receive visits.
指出广告经济与前端滥用工具是臃肿的两大根源
没人愿意为内容付费，所以只能靠广告，而广告主才是真正的客户，对更煽动性广告的需求驱动了这些垃圾。前端开发者也应停止向浏览器发送 20MB 的打包文件和 10MB 的字体。
javajosh查看英文原文
Maybe if you paid for your content it would suck less. The problem is no-one wants to pay for content, so they have to pay for it with ads, which means satisfying the true customer, the advertiser. Google tried, for a while, non-cruft ads, but eventually the demand for more sensational advertising is what drives most of this cruft. Another driver, which is something front-end devs can do something about, is to stop shipping 20MB bundles to the browser, stop using 10MB of fonts, and stop front-loading 200MB of images. Ignorant use of powerful tools that make adding more and more resources to your project feel basically free are a big contributor, at least in the webapp space. (Classic CMS software also accretes cruft, but generally more slowly over time.)
历次讨论
同类还值得读
如今电脑上几乎所有操作在感知上都比 1983 年更慢（2017）
Almost everything on computers is perceptually slower than it was in 1983 (2017)
2017 年的推文串认为，尽管计算机硬件比 1983 年快得多，日常操作的感知速度却常常更慢：启动、界面响应和网络应用被层层抽象、动画、后台检查与网络依赖拖累。
互联网与文化上首页 5 次 · 2017–2020twitter.com网站肥胖危机
The Website Obesity Crisis
Maciej Cegłowski（idlewords）的经典演讲文稿《网站肥胖症危机》，批评现代网页越来越臃肿：动辄数 MB 的 JavaScript、追踪脚本和广告，把本可以轻…
互联网与文化上首页 5 次 · 2016–2021idlewords.com编辑精选亚马逊那本标价 23,698,655.93 美元的苍蝇书
Amazon’s $23,698,655.93 book about flies
博文讲的是亚马逊上一本关于果蝇的二手书被标到 23,698,655.93 美元。
互联网与文化上首页 5 次 · 2011–2022michaeleisen.org浏览器 User-Agent 字符串的历史
History of the browser user-agent string (2008)
2008 年的经典文章用戏谑的“创世纪”口吻，讲述浏览器 User-Agent 字符串如何从简单的标识演变成层层叠加的伪装：浏览器为了绕过按 UA 分发的网站检测，纷纷把自己伪装…
互联网与文化上首页 5 次 · 2012–2022webaim.org编辑精选最后的问题——艾萨克·阿西莫夫
The Last Question - Isaac Asimov
阿西莫夫最著名的短篇科幻小说《最后的问题》的在线全文。
互联网与文化上首页 5 次 · 2009–2019multivax.com编辑精选