Time to market AND only needing half the number of developers (or fewer).

Smaller, more efficient dev teams is a blessing and a curse. Great for business and individual dev job satisfaction. Less great for growing the community.

Better than someone with a name like “Roderick” or “Roxanne” and the name we’d get in that case.

Esolangs need a mention too

Brainf*ck - after Brain from Pinky and The Brain
Whitespace - after Barry White
Rockstar - after Dwayne The Rock Johnson

Who shot first? Han or Greedo?

Although converting it is relatively simple. And there is something to be said for starting with the simplest, least powerful abstraction to reduce complexity.

At any rate, every time I’ve reached for an Agent in production code I’ve ended up needing to convert it to a GenServer before long.

I get where you’re coming from, but the example loses impact as a motivation because www.erlang.org/doc/apps/ert... exists.

This. Almost every event sourcing project I’ve been on has rolled their own ES framework, and that was fine. The complexity isn’t in the accidental complexity of the mechanics of ES, but in the essential complexity of ES *itself*, combined with whatever problem you’re solving.