On Wed, Oct 9, 2013 at 2:36 PM, Ehsan Akhgari <ehsan.akhg...@gmail.com> wrote: > > In the spirit of learning from this, what's next on the chopping block?
JSD. Firebug's the main consumer, AFAIK. > * Most OOM recovery in the JS engine In the past that has been left alone due to the preference of the JS engine module owner. Perhaps the new JS engine module owners can say what they think about it. >>> * XSLT > > We also use it for about:memory apparently. We do? Can you show me where? > In that vein, I think we should take a hard look at the image decoders. At the summit a few of us were talking about ways to promote Rust. One idea was to rewrite a smallish, well-separated component of Firefox in Rust, to (a) gain the benefits (parallelism, safety) of Rust, and (b) promote Rust as a credible language in non-experimental systems. Image decoders were the first component that came up as a possibility. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
