2026-03-26 [09:00:48.0385] https://p.ocmatos.com/blog/jsse-a-javascript-engine-built-by-an-agent.html [09:06:39.0539] > `Array.fromAsync` was the final fix Ah yes, `Array.fromAsync`, the final frontier… [09:08:19.0138] I'm assuming it's because the plan it created roughly ordered recent things by when they were added to the language [09:11:07.0671] Its PLAN.md was apparently generated “from the ECMAScript spec and test262 submodules”, so I wonder how that ordering happened. Not that it matters much. [09:51:03.0393] I wonder if it has garbage collection [09:51:42.0208] if I were given the task to implement a spec-compliant JS engine with no further qualifications I definitely would not add garbage collection [09:58:32.0215] > Claude picked a reasonable feature order, but it made some architectural decisions early on (like how to handle generators, **how to structure the GC,** how to deal with WTF-8 strings) that caused expensive rework later. [10:15:57.0830] was the answer for how to structure the GC: "use a noop" [10:21:37.0189] https://github.com/pmatos/jsse/blob/main/src/interpreter/gc.rs [10:27:21.0269] I do think this is a great benchmark. As the definition is very fixed. It will be interesting what would happen given the same challenge 1 year from now [10:27:45.0840] 1 year is enough time for models to have this repo in their training set [10:28:32.0045] it seems like it attempts GC before every statement: https://github.com/pmatos/jsse/blob/c490bc3fee8c4c8e6b2452f4acacb60d84b02a39/src/interpreter/exec.rs#L112 [10:28:37.0243] which seems both too coarse and too fine