as much as i hate the overhead of frameworks & all the tooling that is (seemingly) required for simple things nowadays, the analogy that is attempted to be made, doesn't really fit well. The author seems to have been too focused on writing a "classic analogy" that has it's own URL rather than writing a good & fitting one for the case he/she dislikes – and especially, putting real thought into the analogy to make it a really good one.
> The author seems to have been too focused on writing a "classic analogy" that has it's own URL
That doesn't track, given the sources at the beginning. One person wrote the essay, then somebody else started hosting it at that URL. There doesn't seem to be a direct connection between the writer and the URL at all.
At least from my own tests, I also found Ebiten extremely smooth and performant when building for the WASM target. There seems to be some people spouting a bit of nonsense in this thread without having actually given Ebiten a chance.
I commented from my experience with ebiten and FFI, and you come claiming it as nonsene because your experience with WASM. Dude, you dont even understand what I brought up then.
Consider options and research properly before choosing tech.
In the case of ebiten + golang, you will suffer greatly from the FFI overhead when calling external graphics API:s.