v0.1.32528 Sep 2026·JavaScript & JIT, Memory & reading

Deep recursion runs like it does in the reference browser

Scripts that call themselves thousands of levels deep, such as tree walkers and recursive parsers, stopped with a stack overflow error at about 2,000 levels in Floati while the reference browser ran them. They now go as deep as the reference browser allows. Calling a list of functions created in a loop is also about twice as fast.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Memory & reading	Recursion goes as deep as in the reference browser. The interpreter allowed 2,000 nested calls, and a function hot enough to be compiled failed near 2,800, because the compiled code counted its own calls against a fixed limit that the interpreter then refused on. The reference browser allows about 7,000 to 11,000. Floati now bounds nested calls by the memory actually left on the thread's stack, hands the rest to the interpreter (which keeps its calls on the heap) and allows 10,000. A script that recurses forever still stops with the same RangeError.
JavaScript & JIT	Calling a list of functions made in a loop is about twice as fast. When a loop calls functions from an array that were all created by the same code (handlers[i]()), the function body is now compiled straight into the loop and reads each function's captured values directly, instead of going through a small interpreter per call: a million calls went from 27 to 15 milliseconds.
JavaScript & JIT	The remainder operator (%) on whole numbers no longer calls the system's floating-point routine. It computes the integer remainder exactly, including -0 where JavaScript requires it (-4 % 2 is -0), and one of our benchmarks got 10 percent faster.