My first 1 or 2 years at Mozilla I spent entirely working on Spidermonkey. I was happy with it, and I even joked that I never wanted to work on the browser proper because compile times were so long compared the to JS shell.
But eventually I branched out and worked on other components, and I'm glad I did because it's given me a much better perspective on things. That's not to say that it's bad if we have people spending all their time working on SpiderMonkey -- it's a hugely important component! But Firefox, in its entirety, is the product that we ship to 100s of millions of users. On Thu, May 12, 2016 at 9:06 AM, Jim Blandy <[email protected]> wrote: > On Wed, May 11, 2016 at 11:31 AM, Bill McCloskey <[email protected]> > wrote: > >> 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. >> > > I feel this way too. > _______________________________________________ > dev-tech-js-engine-internals mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
