On Thu, Jan 2, 2014 at 6:05 PM, Brendan Eich <[email protected]> wrote:
> For me, another key point is that we have various high-frequency crashes >> and security issues in Yarr that we don't know how to fix. >> > > Do we report these upstream? We do, if we actually know that they're upstream bugs. That is not always easy to determine, because in many cases the bug might also be in the adapter layer we use to make Yarr work within SpiderMonkey. Or below that in other parts of SpiderMonkey itself, even. > > > Even if Apple were to fix the most important performance issues, this >> situation wouldn't change meaningfully. >> > > I meant by "contacting Apple" something other than reporting some bugs, > namely mailing the principals and raising the issues of common interest. > One time attempt. I can help. > Understood. The point I was trying to make is that Yarr seems to be largely unowned upstream, and it's pretty much completely unowned (and hard to own) on our end. However, I agree that we should contact JSC people to find out if there are short- or medium-term plans for work on Yarr. _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
