Re: [JS-internals] componentization and specialization, was Re: Clang-format

2016-05-18 Thread Bill McCloskey
On Wed, May 18, 2016 at 2:02 PM, Steve Fink wrote: > The ignorance itself doesn't help, sure. But I still assert that there are > benefits to having fewer things in your head, to have your focus wholly > consumed by a more limited scope for the most part. I'm skeptical that there are any advant

Re: [JS-internals] componentization and specialization, was Re: Clang-format

2016-05-18 Thread Steve Fink
On 05/18/2016 01:38 PM, Bill McCloskey wrote: I think we're starting to conflate separate concepts. I absolutely believe that code should be modular. SpiderMonkey is a great example: we're much more productive because of how well separated it is from the rest of the browser. On the other hand,

Re: [JS-internals] componentization and specialization, was Re: Clang-format

2016-05-18 Thread Bill McCloskey
I think we're starting to conflate separate concepts. I absolutely believe that code should be modular. SpiderMonkey is a great example: we're much more productive because of how well separated it is from the rest of the browser. On the other hand, *people* should not be modular. You don't need to

Re: [JS-internals] componentization and specialization, was Re: Clang-format

2016-05-18 Thread Jim Blandy
There's a lot of value in the Gecko / SpiderMonkey separation. There are certainly other parts of Gecko that would benefit from having clearer boundaries with their surrounding code. The Devtools team is working on establishing such boundaries this quarter, removing all Gecko-specific code (XUL and

[JS-internals] componentization and specialization, was Re: Clang-format

2016-05-18 Thread Steve Fink
Plenty have people have weighed in on the pro-integration side, which I largely agree with, but I think nbp's motivation is valid and worth looking into as an indication of real problems that are only going to get worse if we commit entirely to maximum integration. On 05/12/2016 05:04 PM, Ehsa