ndr

I wonder how more frustrating is it to work on the compiler in rust vs go.

IIRC at the time of the port to go they wanted fast test and compile time, of course it's a different era now.

I keep going in between the two and I'm currently in an Astra season, deeply disliking the tone and modes of Claude.

I wonder if the two will diverge enough that this becomes the tab-vs-spaces/vim-vs-emacs of the LLM era and they'll manage to keep users moving over at some point.

That is linked from the very first line of TFA.

I have a bunch of services running on, perhaps not ironically given your entrypoint was DHH, kamal deployment.

One of them is something I've been hacking on recently: hnfollow.com

But have a whole lot of small services that I run for friends and family too.

I've managed to avoid Go until very recently.

AI + smaller docker images made me look at it again.

The fact I can test/build concurrently and much faster than rust, off the same repo without messing with sccache and worktrees, make it easily the winner for many web/self-contained scenarios.

Monogamy is half the reason this is stable on paper.

Do you happen to have any intuition pump here? Any term of art or class of tests to throw LLMs at to get a sense for these?

Is the solution to a positive swab really to keep swabbing until negative?