> - Add-ons are going to break in both projects. We need to take the developer community's pain into consideration. What is the problem with addons and win64, binary addons? For e10s JS-only addons are problematic as well, so the level of problems we can expect here are quite different.
I don't think we should block win64 on e10s, because even estimating when the project is going to ship to end-users is hard. Cheers, Tom On Wed, Jun 4, 2014 at 8:07 PM, <jmor...@mozilla.com> wrote: > Great point Brian, I should've mentioned the relation to E10S and > sandboxing because as you suggest, it's complicated. > > - E10S and sandboxing help 32 bit users as well as 64 and arguably offer > the most immediate relief to the most users experiencing stability issues. > Most of the folks I spoke with recommended tackling both of those before 64 > if it comes to that. > > - E10S and sandboxing are also more complicated and have a much longer > time horizon to launch. Launching 64 bit first may be a stability bandaid > for users who have 64 bit and adequate memory. It's also security boost for > 64 bit users. > > - Plugin work, as BDS says, is "hard and weird". E10S and 64 compete for > the same engineers here. > > - Add-ons are going to break in both projects. We need to take the > developer community's pain into consideration. > > Those are some big considerations to weigh in resource planning, product, > developer community, and especially in engineering. This feels like the > start of that conversation... > > > > > > On Wednesday, June 4, 2014 1:32:48 PM UTC-4, Brian Smith wrote: > > On Tue, Jun 3, 2014 at 11:37 AM, Chris Peterson > > > > wrote: > > > > > > > > > http://blog.chromium.org/2014/06/try-out-new-64-bit-windows- > > > > > canary-and.html > > > > > > > > > > What is the status of Firefox builds for Win64? When Mozilla releases > > > > > Win64 builds (again), we'll be seen as reacting to Google when we've > > > > > actually been working on it for a while. :\ > > > > > > > > > > > > > Does it make sense to ship 64-bit Firefox before shipping > > > > mutli-process/sandboxed Firefox? I worry that 64-bit Firefox will be more > > > > memory hungry than 32-bit Firefox and if it lands first then it will be > > > > harder to land multi-process Firefox which is also likely to use more > > > > memory. I think having multi-process sooner is more important than having > > > > 64-bit sooner, if there is such a choice to make. IMO, it would be good > to > > > > make explicit choices instead of just shipping whichever is done first. > > > > > > > > Cheers, > > > > Brian > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
