Hi, I'm the one who originally wrote Ladybird's AppKit UI. Just FYI, it was written long before Ladybird split from SerenityOS, and even longer before Swift was on the table. I only chose Objective-C++ because it was the language I was familiar with at the time :)
The specs and the test suite are both moving targets. There are regularly new proposals to the specs, and new tests that cover them as they progress towards acceptance. The main engines implement these proposals behind feature flags, and only enable them once the proposal has been fully accepted.
Ladybird does not hide implementations behind feature flags (yet) because there's no need when you don't have users. So its score on test262.fyi includes all proposals it has implemented thus far.
The other engines on that site have an "experimental options" variant to include these proposals, which is a bit more of an honest comparison. As of right now, that shows: Spidermonkey (Firefox) at 98.3%, V8 (Chrome) at 97.9%, LibJS (Ladybird) at 96.9%, and JavaScriptCore (Safari) at 93.2%.
> However, a jump like that means precisely and exactly what I said it means; very suddenly, that metric became much more important to the team. It is written straight into the graph.
Not really, though. The latest jump was from implementing some CSS Typed OM features, which has been in-progress work for a while now. The 6k increase in the test score was a bit of a happy surprise. It's also not that much of a jump when you zoom out and see it's "just" a continuation of a steady increase in score over a long period.
This is a very strange take. SerenityOS is a hobby project, from which both Jakt and Ladybird were born. Jakt never took off even within the Serenity community. Ladybird is where most of us were spending our time, and its departure from Serenity was a pretty natural evolution.
Ladybird is now a legally established nonprofit, with a board of directors and several full-time employees. Not a hobby.
