[webkit-dev] webkit2 with v8
jake at jakeonthenet.com
Fri Jun 1 10:52:46 PDT 2012
Oliver - Ok, well that makes sense. I was under the mistaken impression
webkit had an engine abstraction, and that it wasn't being move forward to
Darin - If by webkit developer you mean I contribute to webkit, then no. I
do however use webkit in several projects.
On Fri, Jun 1, 2012 at 11:29 AM, Oliver Hunt <oliver at apple.com> wrote:
> 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.
> 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 <darin at apple.com> wrote:
>> On Jun 1, 2012, at 9:55 AM, Jake <jake at jakeonthenet.com> wrote:
>> > I believe it's a disservice to the community as a whole to not provide
>> 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 at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev