JSSE: A JavaScript Engine Built by an Agent
tilt
26 points
12 comments
March 31, 2026
Related Discussions
Found 5 related stories in 54.4ms across 3,471 title embeddings via pgvector HNSW
- JavaScript Is Enough arbayi · 20 pts · March 22, 2026 · 59% similar
- Show HN: µJS, a 5KB alternative to Htmx and Turbo with zero dependencies amaury_bouchard · 124 pts · March 07, 2026 · 51% similar
- A Faster Alternative to Jq pistolario · 375 pts · March 27, 2026 · 50% similar
- Show HN: Jido 2.0, Elixir Agent Framework mikehostetler · 262 pts · March 05, 2026 · 50% similar
- Show HN: Open-source browser for AI agents theredsix · 118 pts · March 11, 2026 · 49% similar
Discussion Highlights (6 comments)
TheRealPomax
Pretty neat as a real-sized-project experiment to see what a programming program can actually do.
pseudosavant
It is pretty incredible to me that in the pre-LLM/agent coding world, creating a new high-quality JS engine or browser seemed like it would likely never happen again. But now, any large company could build one if they wanted to. In a single digit number of months no less.
dmitrygr
Now do it without those pre-written tests. Spec only. Else, the writers of those tests deserve a LOT of credit.
Waterluvian
This is really cool to see and study. It’s a great experiment. I think it doesn’t really say a lot though. The hard part, in my opinion, is not making a new engine, it’s making one that’s worth using and will remain so for a long time. What I’d love to see next is how well (or poorly) this approach is at making the performance not terrible.
Imustaskforhelp
Great. the one-agent-one-human repository by embedding-shapes is certainly quite nice and I had tried to re-create the results (within golang) though and I had failed but even within that I feel like maybe I learnt a lot of things (Also got to talk with emsh on bsky!) It will also be very interesting to read simonw's comments on all of this too ( https://news.ycombinator.com/item?id=46779522#46786824 ) when he had said:- No, I'm still waiting to see concrete evidence that the "swarms of parallel agents" thing is worthwhile. I use sub-agents in Claude Code occasionally - for problems that are easily divided - and that works fine as a speed-up, but I'm still holding out for an example of a swarm of agents that's really compelling. The reason I got excited about the Cursor FastRender example was that it seemed like the first genuine example of thousands of agents achieving something that couldn't be achieved in another way... and then embedding-shapes went and undermined it with 20,000 lines of single-agent Rust! (I wonder what Simon thinks now of this, because from my skim of this article, they do seem to mention some tidbits about parallelism, Either way, I think that these projects are really adventurous and there is still something novel in all of this.) (Edit: I have tried reading the blog post many times now but I am unable to understand how this is [working?] but something like cursor's project had turned to waste. Initially people were optimistic about cursor's project until emsh really showed them that it wasn't so good, I hope that this might not be the case here but still, I am just a bit confused as to why this in particular seems to work, kind of waiting for simon's post about it now :] )
ivankra
They really did manage to benchmaxx test262 and beat everyone at it. In my testing (all engines with experimental flags in same conditions on full test262): 99.5 jsse 99.1 v8 99.0 spidermonkey 98.1 libjs 97.4 escargot 97.3 jint 96.4 boa 95.0 graaljs 93.2 kiesel 92.1 jsc 82.8 quickjs 82.5 quickjs-ng 82.1 xs 80.1 brimstone 77.7 nova 74.6 jerryscript 66.5 sobek 65.5 goja It ain't fast (~10x slower than boa), but very compliant.