Earlier quoted context omitted.
> complex standards to be well specified in human language instead of in code so a reference implementation is what will always win in the end. > At least chromium is open source. That source code is 12-15 million lines of code. They implement literally thousands of specs. Chrome adds 40-70 new web APIs [1] with each release which happen roughly once every 40 days and contain god knows how many code changes. Good luc…
>That source code is 12-15 million lines of code. Exactly, it's impossible to describe that in human language which doesn't have precise enough semantics. That's why the spec has to be in code, in the form of a reference implementation and/or test suit. The goal should be to move chromium away from being controlled too much by Google.
On the contrary, this implements specs that are defined in a human language. For example, the full semantics of rendering HTML were standardised with HTML5, and now all browsers render HTML the same way.
The problem isn't the human language. The problem is the sheer number of these specs. Hundreds, if not thousands.
However, good luck understanding these specs by reading code or unit tests (and yes, there's a multitude of tests [1]). How do you know what a piece of code encodes? Or a test tests? You really propose to reverse engineer behaviour from code?
Example: here's a test: https://github.com/web-platform-tests/wpt/blob/master/html/s...
What exactly does it test? Why? Is this a correct test for this behaviour? Care to pinpoint the exact precise location of this spec in Google Chrome's code? [2] It's only 12 or so million lines of code, should be easy to find.
> The goal should be to move chromium away from being controlled too much by Google.
By doing what exactly?