On Mon, Aug 01, 2011 at 10:09:25AM -0700, Nayan Kumar K wrote: > Hi there, > > We have ported V8 to WebKit-GTK, gitorious repository with these changes is > at - https://gitorious.org/~nayankk/webkit/nayankk-webkit. > > Compilation of WebKit-GTK with V8 can be turned on using, > > sh autogen.sh --with-jsengine=v8 > > Patch has been uploaded at https://bugs.webkit.org/show_bug.cgi?id=32452 > > We would like to push these changes to WebKit, of-course once it gets > reviewed. :) > > Let me know your opinions/concerns. >
We have discussed about this in the past, the conclusion was that adding all this code without a good reason is not that interesting, our understanding is that in big projects with long story you have to care about the code maintainability not just adding features. It will add more work to maintain the port and more complexity when trying to do some things. And basically performance tests were showing we have both engines in the same ballpark so choosing one or the other will not give any benefit to the user. Anyway if you want to push this patch I would say the best option is that you try to show how this is a big improvement or that it will be a separate part of the code that will not cause any issue. But this is just my understanding of what was the situation. Btw, usually in this kind of patches the best idea before starting to work is asking to the people that was already checking it why it was stopped. Hope it helps. _______________________________________________ webkit-gtk mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-gtk
