HN user

overflowy

186 karma
Posts13
Comments39
View on HN

This is basically the setup I ended up using after trying to check the following boxes:

- using GPT‑5.6‑sol via OAuth instead of an API key, with Claude Code as the harness

- sandboxing the reviewer agent completely (GPT‑5.6‑sol seems to be a model that believes "the end justifies the means", I read tons of horror stories on X and Reddit)

- using herdr to view and control the current process of the review agent (can jump in at any time)

- the main agent can refute certain points made by the reviewing agent

Basically any data grid that implements multiple AND/OR filters at column level, sorting, reordering, infinite scrolling, virtualization for handling large amounts of data, etc. Also handling basic pending / error / retry states (things that I take for granted with React Query).

While I love both Go and Alex, my experience with HTMX has always ended up being disappointing.

I think the best way to put it, when I'm working with HTMX it feels like the complexity of the codebase is growing at a 2:1 rate compared to the app itself. I always end up with some weird edge case that I can not come out of without some weird hack.

I get why people dislike Node packages, HTMX feels like it's an overcompensating response to that. But the time you save by not having to wrestle with JSON is tripled when you try to make the app actually look or feel good. It takes me 2 minutes to slap together a Mantine template [1] and tap into some of the best UI components, then I can embed the built static assets and end up with the same single Go binary.

[1] https://github.com/mantinedev/vite-min-template

At this point, this all feels like marketing, people getting paid left and right to make all kinds of claims about this model as long as it stays in the spotlight.