Google and Apple's engines are open source (and Microsoft now contributes to Google's). What would be the benefit of a separate reference implementation of thi

Google and Apple's engines are open source (and Microsoft now contributes to Google's). What would be the benefit of a separate reference implementation of this standard? I suppose it would be easier to port to other browsers if it were designed as a standalone library rather than tightly integrated into an engine. But the idea of going to pains to design a standalone library seems to contradict your later statement that you want an entire reference browser. A web browser is orders of magnitude more complex than a video encoder or a Wayland server. Not aiming for high performance would make a browser a little less complex, but not by much, so there doesn't seem to be much point. Minus that, you're just asking for someone (who?) to write a new web browser from scratch. It would certainly be nice if there were more independent web browser codebases in general, but I don't see what special benefit a new one would bring to the table just due to being marked as a "reference implementation".