News for hackers. Stuff that matters.
Re:Mozilla Reaction to U.S. vs. Google by jcranmer on Wednesday October 21, 2020 @12:44AM (#24844794)
The only way that makes sense is if you kill off Gecko (or, more bizarrely, Blink/Chromium). which cuts the number of browser vendors down to a very lopsided 2. And you end up with a very complicated, extremely essential piece of modern computer infrastructure reliant on a single underfunded organization--which is the sort of situation that resulted in the OpenSSL failures that led to Heartbleed.
Re:Mozilla Reaction to U.S. vs. Google by gkoberger on Wednesday October 21, 2020 @12:50AM (#24844820)
Well, I think that would be the goal.

Right now, a ton of vendors spend a lot of time on negotiating standards, which are written in English. And then that English is translated into code. And at this point, it's really just for the sake of Gecko – every other major player just uses a derivative of Webkit.

So, if you had Mozilla take stewardship over Blink, you wouldn't really need a "standard" anymore. Everyone could just use the same rendering engine, and the code itself would act as the "standard". Each vendor could then build their own chrome around it.

Instead of everyone trying to implement the same stuff the same exact way in multiple rendering engines, forces could be combined.

Re:Mozilla Reaction to U.S. vs. Google by whatshisface on Wednesday October 21, 2020 @10:27AM (#24848189)
The standard is also for the benefit of web developers. In fact, they need it more than even the browser vendors.
Re:Mozilla Reaction to U.S. vs. Google by gkoberger on Wednesday October 21, 2020 @02:49PM (#24850818)
At that point, wouldn't it just be called documentation?
Re:Mozilla Reaction to U.S. vs. Google by whatshisface on Wednesday October 21, 2020 @03:02PM (#24850933)
Web developers participate in the negotiation process.