[webkit-gtk] Porting V8 to WebKit
roger.wang at linux.intel.com
Wed Nov 9 23:44:57 PST 2011
On Fri, 2011-10-07 at 20:21 +0800 Nayan Kumar K wrote:
> Sorry to open up this discussion again, :) Based on the recent developments
> in bug https://bugs.webkit.org/show_bug.cgi?id=32452 and
> https://bugs.webkit.org/show_bug.cgi?id=69469, it seems like some are keen
> on having V8 as an configurable build option in WebKit-GTK.
> One obvious advantage of using V8 in WebKit-GTK is faster JS engine (at this
> point of time!). Moreover, it will be provided as separate build option and
> SFX will continue to be the default JS engine. If we ever in future wish to
> shift completely to V8, such transition would be smoother.
> On the down-side, I understand the concern about code maintainability and we
> are ready to maintain any code changes that are added for V8.
> Please let me know your suggestions, concerns, comments and feedback, we
> will try to address them and conclude on whether to push this patch or not.
Thank you for your work.
Here we're developing a WebKit module for NodeJS so people could write
native applications with web technology, utilizing various NodeJS
libraries. And having a WebKit/V8 makes the project possible - in order
to have JS code from WebKit call JS code in NodeJS, the 2 V8 contexts
(from WebKit and NodeJS) were merged somehow. It's not possible to do
this between 2 different JS engines.
Roger WANG Intel Open Source Technology Center
More information about the webkit-gtk