From:  Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date:  13 May 2016 22:19:49 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.tech.js-engine.internals
Subject:  

Re: Clang-format

NNTP-Posting-Host:  63.245.214.181

On 2016-05-13 8:01 AM, Anthony Ramine wrote:
> On Friday, May 13, 2016 at 2:04:25 AM UTC+2, Ehsan Akhgari wrote:
>> The current reality how web browsers are made don't afford us treating
>> our codebase in that way any more.  To me, discussions around unifying
>> the coding style drill into the heart of this problem: we need to move
>> on from having small compartments with people painting the walls to
>> their heart's content, and treat the browser as the one unified beast
>> that it truly is.  Not because it matters how much whitespace we put
>> where, but because a unified style paints the walls in a way that urges
>> people to stop thinking in terms of small islands, and start thinking in
>> terms of Firefox as a whole.
> 
> What about V8, Chromium and Node.js? Safari and WebKit and JSC? Edge and Chakra?

The same goes pretty much for V8 and Chromium (Node.js using V8 is
mostly work done by people not working on a browser, so isn't relevant
to the topic at hand.)  It's hard to say how much of this is true for
Safari and Edge given they're both closed source, but as far as WebKit
goes, downstream consumers not using WebKit for Safari typically have to
spend a ton of effort keeping up with WebKit changes due to the needs of
Safari.