On Tue, Jan 23, 2018 at 04:50:10PM -0800, Gregory Szorc wrote: > On Tue, Jan 23, 2018 at 4:34 PM, Gregory Szorc <g...@mozilla.com> wrote: > > > What we don't generally know is the impact requiring Node.js would have on > > downstream packagers. Our adoption of Rust last year was a long and > > sometimes painful process. I have a feeling that requiring Node.js would be > > a similar experience. But like Rust, I feel that adopting Node.js is in the > > best long-term interest for Firefox development velocity and product > > quality. I'm reluctant to cause more hardship by introducing a new build > > dependency. But it's very difficult to keep saying we can't use Node.js in > > the Firefox build system. I wish I could say "we'll build SpiderMonkey and > > use that instead." Unfortunately, many Node.js tools don't work with > > SpiderMonkey, so that's not an option. Plus there are difficulties with > > cross-compilation. As sad as it makes me to say it, SpiderMonkey is not an > > option: Node.js is the only viable option. > > > > If we require Node.js to build Firefox, what are the requirements, > > desires, and hardships of downstream packagers and consumers of the Firefox > > build system? Keep in mind that mozilla-central right now is Firefox 60. > > That will become ESR 60 in May. > > > > Quick follow-up. First to add mozilla-linux-taskforce. Second to note that > we almost certainly wouldn't make a change before Firefox 61. That would > give everyone only caring about ESR an extra ~1 year to deal with fallout.
The adoption of rust has been painful, i guess the requirement of npm will be even more painful, and if i'd be given the choice, i'd strongly raise my voice against it. Just recently it's been made harder for packagers to work on betas by not providing source tarballs anymore but only a link to hg that we get to hammer (#1432591) and now this ? But since the decision has already been made, i guess we can't do anything about it, but adapt or die ? As long as the required version isnt too recent (we have 6.12.3 in OpenBSD right now, and i have no idea what this means in terms of nodejs versions) and *you stick to vendoring the nodejs modules HELL* (build systems are forbidden to download stuff themselves here), i guess we'll swallow the bitter pill. Or give up and go do something else, in the greener pastures outside of this crazy javascript bloat ecosystem. Landry _______________________________________________ dev-builds mailing list dev-builds@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-builds
