Friends, Wo-mans, pythonistas… lend me your tokens. I’m building Chromonic, an experimental Python browser/rendering engine, mostly by throwing Claude at increasingly unreasonable problems: https://github.com/byteface/chromonic/ It uses Dom...
Friends, Wo-mans, pythonistas… lend me your tokens.
I’m building Chromonic, an experimental Python browser/rendering engine, mostly by throwing Claude at increasingly unreasonable problems:
https://github.com/byteface/chromonic/
It uses Domonic as its DOM/CSSOM and now has a Chrome-vs-Chromonic layout conformance harness, which means I can feed it real web-platform tests and objectively measure how wrong my browser is.
Naturally, I would now like to outsource that wrongness to your Claudes.
If anyone has some spare tokens and fancies joining the campaign:
cd tests/layout
Clone WPT:
git clone --depth=1 https://github.com/web-platform-tests/wpt.git
Then point Claude at a folder under WPT/CSS2 and basically tell it:
Run the tests. Find why Chromonic disagrees with Chrome. Fix it. Repeat until victory or bankruptcy.
If the problem is actually in Domonic upstream, add it to PLAN.md and patch around it locally for now.
Pick whatever CSS2 area takes your fancy. Different agents attacking different folders would be especially interesting.
PRs, battle reports, pass-rate improvements and tales of token expenditure all welcome.
The browser is unfinished, the standards are enormous, and I have made the questionable decision to see whether a small army of Claudes can brute-force CSS conformance.
Who’s in?