Re:JavaScript performance, WebAssembly, and Shared Memory in...
by WorldMaker on Friday April 21, 2017 @11:03AM
(#14166182)
Yes, that was exactly my point. Browser monocultures create good, bad, and ugly results. As I pointed out with both of my examples: we standardize the good ones, complain about the bad ones, and try to ignore the ugly ones. I am accusing the Chrome monoculture of creating the same sort of environment. As I posted: then no one else can move forward without first guaranteeing "Chrome compatibility" rather than spec compatibility.
The web has a long history of post-facto standardization where implementation comes before standardazation (see browser wars).