webframe evaluated as a fast, lightweight browser script runner

Summary

Simon Willison had Claude Opus 5.5 evaluate Jeff Lindsay's Go-based webframe tool. This utility runs web pages in a hidden system browser view and pipes console output to stdout. The verdict: It is fast and lightweight for data scraping, comparable to shot-scraper. However, it is riddled with issues such as CSP errors, a 0×0 viewport, and stuck loads.

Why it matters

The tool offers a system-browser-based alternative for executing JavaScript in a headless context without requiring Playwright. This feature is significant for lightweight data scraping and sandboxing pipelines that wish to avoid heavy browser engine dependencies. The Go + glaze architecture (WKWebView / WebKitGTK / WebView2) could be a practical deployment option for CI or server-side JavaScript execution where Chromium packaging is unnecessary.

Highlights

• Written in Go using the glaze library; it reuses the operating system's native web view instead of packaging a browser engine
• The evaluation revealed real-world errors: CSP violations, 0×0 viewport size, stuck loads, and missing HTTP headers
• Positioned as a lighter alternative to shot-scraper's Playwright-based JavaScript executor

Critical take

The evaluation was conducted by Claude Opus 5.5, a large language model (LLM), rather than a human engineer. This raises questions about whether subtle rendering or network edge cases were truly tested. Furthermore, the article reads more like a promotion of a full research report than an independent assessment. It fails to provide concrete comparisons or reproducible test scenarios to the reader.