On Thu, Jan 2, 2014 at 5:14 PM, Brendan Eich <[email protected]> wrote:
> > What about contacting Apple principals who maintain JSC and checking > whether they want to fix YARR? Just because their bug has been idle for > years does not mean we should assume they aren't thinking of, planning, or > even about to start working on JITting all the regexps. > There hasn't been any meaningful amount of activity in Yarr for a long time now. We reported various issues, sometimes with pointers to easy fixes we applied, without ever getting even an aknowledgement. 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. Even if Apple were to fix the most important performance issues, this situation wouldn't change meaningfully. On Thu, Jan 2, 2014 at 4:31 PM, Nicolas B. Pierron < [email protected]> wrote: > In addition, one might even suggest that we self-host the regex compiler. If this is not a performance issue, I think this would be a good idea as the first persons who are willing to get features in the JavaScript Regex engine are JavaScript users. It's probably no surprise that I like this option. One thing we could do to evaluate its potential is to replace the regexps in some benchmarks with straight-forward, not-too-clever JS implementations and see what the resulting performance and memory characteristics are like. _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
