On Tuesday, June 05, 2012 08:12:01 AM ext Coda Highland wrote:
On Tue, Jun 5, 2012 at 7:53 AM, Balazs Kelemen kbal...@webkit.org wrote:
Hi all!
I think it's time to decide how important is the v8 integration for us.
I'm
not saying it's hyper-super important, I'm just curious about
On 06/13/2012 05:44 PM, Simon Hausmann wrote:
On Tuesday, June 05, 2012 02:53:19 PM ext Balazs Kelemen wrote:
Hi all!
I think it's time to decide how important is the v8 integration for us.
Yes.
I'm not saying it's hyper-super important, I'm just curious about your
opinion. In fact we
Hi all!
I think it's time to decide how important is the v8 integration for us.
I'm not saying it's hyper-super important, I'm just curious about your
opinion. In fact we have a qt5 release blocker bug for that:
https://bugs.webkit.org/show_bug.cgi?id=76778 (although at the time when
it
05.06.2012, 16:53, Balazs Kelemen kbal...@webkit.org:
Hi all!
I think it's time to decide how important is the v8 integration for us. I'm
not saying it's hyper-super important, I'm just curious about your opinion.
In fact we have a qt5 release blocker bug for that:
On Tue, Jun 5, 2012 at 7:53 AM, Balazs Kelemen kbal...@webkit.org wrote:
Hi all!
I think it's time to decide how important is the v8 integration for us. I'm
not saying it's hyper-super important, I'm just curious about your opinion.
In fact we have a qt5 release blocker bug for that:
But V8 is the engine of QML so if you use the QML API of QtWebKit for
Qt5 then V8 is loaded de-facto.
snip
QML developers moved away from JSC (Qt4) so they will not move back for sure.
snip
V8 apparently was faster for QML use cases.
snip
Apparently QML guys does have a lot of benefits using
On Tue, Jun 5, 2012 at 10:51 AM, Coda Highland chighl...@gmail.com wrote:
I don't understand why the push for V8 in the first place. JSC and V8
are in an arms race for performance, so you can't categorically say V8
is faster because that's not always true.
I did not say it's faster or
Hello,
On Tue, 5 Jun 2012 14:53:19 +0200
ext Balazs Kelemen kbal...@webkit.org wrote:
Anyway, I would not like to make the false illusion that pushing these
patches will solve every problem and just save memory. In fact, in order
to get the desired benefit we have to solve other issues: