[Sugar-devel] webkit, hulahop; developing apps using browser engine DOM for widgets

[Lucian Branescu]

Not now, I have my own work to do for GSoC.

I have talked to tomeu about what it would take to give Browse the
ability to switch between engines. The general conclusion was that
another layer of indirection would be needed, on top of
hulahop/pywebkitgtk that Browse would use.

Hand tuning or not, the JavaScript engine in webkit (or v8) are
significantly faster than Tracemonkey, that's for sure.

2009/6/10 Martin Langhoff <martin.langhoff at gmail.com>:
> On Wed, Jun 10, 2009 at 7:55 PM, Lucian
> Branescu<lucian.branescu at gmail.com> wrote:
>> I don't think I have the results anymore, but benches between
>> epiphany-webkit and epiphany-gecko were very similar.
>
> Lucian -- what Jonas and I are trying to say is: even if gecko is
> (was?) by less "performant" than webkit on a standard machine and
> using gecko's default settings, you _have_ to test tuned gecko vs
> tuned webkit.
>
> "Out-of-the-box" performance isn't what matters to the end user.
>
> I agree with you, the usual perception is that opera and webkit
> engines are faster / lighter than gecko. But right now, gecko-based
> Browse.xo is noticeably faster than opera.
>
> Can you prepare a hand-tuned webkit-based Browse.xo so a reasonable
> comparison can be made?
>
> cheers,
>
>
>
>
> m
> --
>  martin.langhoff at gmail.com
>  martin at laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff
>