If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I know this has been in the works for a while. Good stuff. The only downside to v8 versus mozilla's engine is they tend to be a bit more conservative about features. v8 doesn't have all the fancy JavaScript 2 stuff like the nice Python-like iterators and such. Decent ES5 support though so I can't complain. It'll be a step up from the current javascriptcore.

I've gotta say I'm more looking forward to the updated Qt-webkit in Qt 4.8 than I am to the v8 engine. The current Qt-webkit is really showing it's age. (It was forked from mainline Webkit years ago and never updated.)

Comment

While V8 is fast, Chromium crashes with wild abandon on my 32-bit installations of Kubuntu and with annoying frequency on the 64's. Rekonq, which uses WebKit, but a different JS engine I believe, is a rock. Throw multiple windows with multiple tabs all loading at once its way and it just purrs along.

Of course, making it all better on Chromium is a cutesy, Star Trek-inspired, "He's dead, Jim" failure alert. I wonder if that will become par for the course for KDE users?

Comment

While V8 is fast, Chromium crashes with wild abandon on my 32-bit installations of Kubuntu and with annoying frequency on the 64's.

I've seen JavaScript-heavy (used for auto-updating the content etc.) pages crash in Chromium if you leave them open for several days, but not all that often. (But I don't use Chromium much?it's not ready for the workload I throw at Firefox...)