Very much agreed on all these points. Also, beyond fixing bugs,
crossing components often allows for fundamentally simpler and more
(Also, fwiw, 2-space indent seems fine, even preferable, to me.)
On Wed, May 11, 2016 at 1:31 PM, Bill McCloskey wrote:
> On Wed, May 11, 2016 at 5:01 AM, Nicolas B. Pierron <
> firstname.lastname@example.org> wrote:
> If the problem are the pointless arguments on dev.platform, which are
>> mistakenly considering SpiderMonkey as Gecko's property, I would totally
>> agree on moving SpiderMonkey into its own repository.
>> I do not see how indentation differences could be a speed bump, and even
>> if this was a problem, I am still not yet convinced this alone could
>> justify changing 95% of the lines of the project.
>> One thing I hate with Gecko undesired continuous integration, is that we
>> are hold responsible for failures in tests that we cannot reproduce. Having
>> a separated project would make explicit the fact that someone is
>> responsible for the integration, and for converting such test cases into
>> SpiderMonkey test cases. I honestly think I spend more time thinking about
>> how I can reproduce some Gecko failures than anybody spent else spent about
>> thinking about indentation.
> This is a really bad attitude for Mozilla as a whole. Every one of us at
> Mozilla has a responsibility to make Firefox the best web browser. The more
> we divide ourselves into cliques and label bugs as "someone else's
> problem", the sooner we will fail. You might think it's more productive for
> you to focus on SpiderMonkey alone and let other people deal with other
> issues. Unfortunately, many of the most important bugs that span across
> different areas; with your approach, these bugs will never be fixed.
> Mozilla needs more people who understand multiple browser components. I'll
> call them superheroes because of how valuable they are. Understanding and
> reproducing browser tests can seem unrewarding, but it's a great way to
> start to understand how the rest of the system works. People on the
> SpiderMonkey team are in a great position to be superheroes: SpiderMonkey
> and XPConnect are some of the hardest parts of the browser to understand,
> and it's often necessary to step through them to debug other browser
> issues. People who already understand them have an advantage over everyone
> else. Shu has done a great job with stuff like this lately, and it would be
> great if more JS devs stepped up in the same way.
> I'm sorry to be so corny and didactic, but I've been feeling really
> strongly about this problem given all the troubles that have arisen between
> the platform and front-end teams lately. We all need to stick together and
> be one Mozilla. Splitting SpiderMonkey into a separate repo is the absolute
> last thing we should be doing.
>> Nicolas B. Pierron
>> dev-tech-js-engine-internals mailing list
> dev-tech-js-engine-internals mailing list