They may have a desire for it, but certainly not a need -- Webkit includes a well maintained, guaranteed ABI stable JS engine that works on _all_ architectures, with a high performance JIT support available on numerous architectures and OS's. Being able to support two engines just in webcore has added substantial complexity to the codebase, and has led to many features being implemented only for one engine but not the other. There is a very large and substantial cost to this, and very little actual benefit.
We have repeatedly stated that support for JS engines other than that provided by webkit is not a primary goal of webkit, and ports that wish to make use of any other engines do so at their own risk, and there attempts to do so can't interfere with the actual webkit project. --Oliver On Jun 1, 2012, at 10:12 AM, Jake wrote: > What constitutes a need? Qt obviously has a need for it. Is there a threshold > of ports needing a feature before it becomes blessed? > > > On Fri, Jun 1, 2012 at 11:09 AM, Darin Adler <da...@apple.com> wrote: > On Jun 1, 2012, at 9:55 AM, Jake <j...@jakeonthenet.com> wrote: > > > I believe it's a disservice to the community as a whole to not provide > > proper javascript engine abstractions in webkit. > > I don’t agree. > > We should have abstractions for things that need to be abstract. Too many > abstractions make the code much harder to work with. > > -- Darin > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
