[rapind]

For me this is Gleam. Fairly small lang, type safe, compiled, NO NULLS (very important IMO), good FFI, code is readable, and... you get the BEAM!

Agents can pretty much iterate on their own.

The most important thing for me, at least for now (and IMO the foreseeable future) is being able to review and read the output code clearly. I am the bottleneck in the agent -> human loop, so optimizing for that by producing clear and readable code is a massive priority. Gleam eliminates a ton of errors automatically so my reviews are focused on mostly business logic (also need to explicitly call out redundant code often enough).

I could see an argument for full on Erlang too, but I like the static typing.

[shakna]

How's Gleam's IO story today? Still need to go via OTP?

[rapind]

Under the hood you're still calling into BEAM/OTP but most operations are covered in gleam, at least I've very rarely needed to FFI into Erlang (couple times to extend what a library provides with a custom edge case).

gleam/io, mist, gleam/otp, sqlight, gleam_pgo, etc.

[shakna]

gleam/io doesn't actually support file IO, though, does it? Only printing to stdout.

So you'd need to use FFI just to write to disk, right?

[rapind]

There’s simplifile

[dnautics]

no nulls is truly not a problem. Of all the problems I have seen, I have never seen Claude mess up with nulls in Elixir.