博客

Lightpanda 10 月 19 日的从零浏览器表里没有 AginxBrowser。同一道 940 页 Amiibo、25 路，这台 Mac 上 0.6.2 三次冷启动 51.6–52.4 秒，峰值 RSS 约 400 MiB。对手 10 月 22 日没有重跑。4.5 秒留在他们的 AWS 表里。

Their from-scratch table left AginxBrowser out. Same 940-page Amiibo crawl, pool 25, this Mac: 0.6.2 at 51.6–52.4s and about 400 MiB RSS. Peers were not re-run on Oct 22. The 4.5s figure stays on their AWS table.

一个 35k star 的 Zig headless 浏览器发了 0.4.1，我对着它的 release notes 翻自己的 git log：这周它开票的几个东西，我们几天前就 ship 了。不放形容词，只有时间戳和链接——包括一条他们比我们先开票的，照样放进表里。活版记分牌在仓库 docs/RECEIPTS.md。

A 35k-star headless browser shipped 0.4.1; reading their release notes against our git log, several things they filed tickets for this week we had shipped days earlier. Timestamps and links only — including the row where they filed first. The living scoreboard lives in docs/RECEIPTS.md.

单二进制、零 Chromium 的承诺逼出了一条不一样的截图路径：自己 V8 跑完 JS，再喂给 Blitz（Stylo + Taffy + parley + vello_cpu）布局绘制。文章记录全白屏的根因链（上游 #636）、CJK 挂死的钉版决策（parley#752）、以及元素坐标实现里 paint_scene 裁剪的自相矛盾。

Kitesurf 验证了「Agent 需要自己的浏览器」这个判断，也公开承认了硬缺口——真实 TLS 指纹、有状态登录会话。恰好是 AginxBrowser 从第一天就在啃的（再加上纯 HTTP API）。

The blank-screen root cause, the CJK hang, and the coordinate-crop trap — a full post-mortem of building screenshots on Dioxus Blitz with zero Chromium and no GPU.

Kitesurf validated that agents need their own browser — then openly listed the three hardest things it won't do. Those are exactly what AginxBrowser was built for.