Erick ๐ Navarro retweeted
lol my lawn mower is only used 1x a week. Should I rent one from OpenAI instead?
Also, who caused the DRAM shortage? It wasn't consumers...
sam: local inference is a terrible allocation of scarce resources
โa lot of people want local inference, and somehow they assume that the problem is solved now because we have open-source models, we're going to be able to run them on our computers, and so we're not going to need all the stuff in the data centre
but from a global allocation perspective, actually it's quite terrible to have everybody, like, have a bunch of the world's limited supply of DRAM sitting in their own computer and being used five percent of the time
you want maximum utilisation in the cloud if you're trying to deal with this very supply-constrained environment
somehow many people's intuition is the opposite of thatโ
Erick ๐ Navarro retweeted
So I was trying to understand why pull requests speeding up the Elixir version were being denied by the clankers while they were being accepted to Go/Express/Rust.
It turns out that, not only each project had a different starting point and a different prompt, but also each project also has a different set of verifications that they are required to pass!
For example, Elixir is the only guided to "preserve the pinned Rails reference behaviour", the only with a explicit verification that we are using Redis and draining its queue (so we cannot remove it while others can), and the only one actively enforcing it.
So it turns out that the people telling you to not read the code cannot even use AI to set up fair benchmarks (probably because they would have to read the code in order to do that).
You don't have to believe me, you can do your own research or ask your agent to do it for you. E.g. here is what Claude Code came back with: gist.github.com/josevalim/aeโฆ
Replying to @dhh
Also extracted a separate verification project that's responsible for the benchmarking and checking of new implementations and improvements to the existing ones. The full report from the latest runs is there too. github.com/basecamp/once-camโฆ
Erick ๐ Navarro retweeted
Oh FFS. It turns out the req/s in the initial vibed Rust version is within the same order of magnitude as the initial vibed Elixir/Go versions, and even performs worse in some of them.
The history is in the repository! The Rust version only got faster with a bunch of additional work. The initial Elixir/Go versions presented in the tweet below saw none of this additional work. It was comparing a 300 commits Rust version with a 2-3 commits Elixir/Go version.
Source: github.com/basecamp/once-camโฆ
I've had agents implement and optimize the Campfire web app in Elixir, Go, and Rust. Yes, Ruby is the slowest. I didn't care about that when the pay-off was huge in terms of productivity and developer joy. But if you're no longer reading the code? github.com/basecamp/once-camโฆ
Readers added context they thought people might want to know
The shown benchmarks use non-equivalent implementations: Elixir routes all DB queries through a single GenServer with Redis for jobs (retained from Rails), while Rust uses in-process queues, omits CSRF tags/fields, and applies other caching changes.
github.com/basecamp/once-โฆ
raw.githubusercontent.com/basecamp/once-โฆ
github.com/basecamp/once-โฆ
github.com/basecamp/once-โฆ
x.com/zachsdaniel1/sโฆ
Erick ๐ Navarro retweeted
If you'd used Emacs, you would never have had to switch away to begin with.
Erick ๐ Navarro retweeted
all linux distros are just piles of bash scripts
except for nixos, which is configured using an advanced lazy functional programming language...
...which evaluates to a pile of bash scripts
Hi @Pebble, why do I need an account to be able to see battery usage? ๐ค
137
Trying Jujutsu #jj for a Week
erick.navarro.io/posts/tryinโฆ
78
Cuando el junior(deepseek-v4-flash) no encuentra el error y llamas al mid(deepseek-v4-pro) y tampoco lo encuentra y toca llamar al senior(glm-5.2) que cobra mรกs caro
Erick ๐ Navarro retweeted
Elixir v1.20 released! Now officially a gradually typed language: Elixir type checks every single line of code, finding bugs and dead code, without developer overhead (no typing signatures) and extremely low false positives rate. Plus a faster compiler! Links and reports below.























