Regardless of where jakt goes, it would never be qualified for this; Ladybird is doing its best to get rid of everything home-built that is not the web-platform.
(Also it's a really young language with <5 recurring contributors, of course it's not even on the radar :)
> you don’t—you never—pick and choose based on “that thing is obsolete and no one uses it anyway
This might make sense for a complete implementation, but in reality...no one would implement a useless API.
Also, if truly no one used it, it would simply not exist (e.g. `with` in module mode), a new implementation of some spec will always pick and choose based on utility and use-cases.
(Also it's a really young language with <5 recurring contributors, of course it's not even on the radar :)