Linked by Thom Holwerda on Sat 6th Sep 2008 19:56 UTC, submitted by KAMiKAZOW
Internet & Networking

The WebKit team is currently busy, integrating the patches made for Google Chrome into the main WebKit repository. This includes the new V8 JavaScript engine and the Skia graphics library. Most integration work is done by Google employee and WebKit reviewer Eric Seidel. V8 is a fast, BSD licensed JavaScript engine that runs on 32bit x86 and ARM CPUs. Due that platform restriction, V8 probably won't replace WebKit's new SquirrelFish engine anytime soon as default, because SquirrelFish has broader CPU architecture support. Epiphany developer and WebKit reviewer Alp Toker gives an overview about Skia. Unlike V8, Skia is licensed under the Apache License 2.0. Some of Skia's main features are optional OpenGL-based acceleration, thread-safety, 10,000 less lines of code compared to Cairo, and high portability.

Thread beginning with comment 329483
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Porting V8 to x64
by lucabotti on Sat 6th Sep 2008 23:00 UTC in reply to "Porting V8 to x64"
lucabotti
Member since:
2006-01-03

if any effort at all...actually, if v8 is Leopard Mac OS X compatible, than, given that Leopard is only 64 bit (x86_64)...

I find quite strange the assumption of linking vs 32 bit libraries (see the issues on v8 site).

Reply Parent Bookmark Score: 1

RE[2]: Porting V8 to x64
by patrix on Sat 6th Sep 2008 23:17 in reply to "RE: Porting V8 to x64"
patrix Member since:
2006-05-21

I find it strange that people say Leopard is 64-bit only, as I run it very well on my 32-bit Macbook first-gen Macbook...

Reply Parent Bookmark Score: 2

RE[3]: Porting V8 to x64
by Chezz on Sat 6th Sep 2008 23:59 in reply to "RE[2]: Porting V8 to x64"
Chezz Member since:
2005-07-11

they are stupid

Reply Parent Bookmark Score: 3

RE[3]: Porting V8 to x64
by ba1l on Sun 7th Sep 2008 00:33 in reply to "RE[2]: Porting V8 to x64"
ba1l Member since:
2007-09-08

They're actually not that far wrong.

On Tiger, the entire OS was shipped as fat binaries, containing code for PowerPC and x86. On Leopard, those fat binaries also contain code for 64-bit PowerPC, and x86-64.

If you have a 64-bit capable CPU (like the newer Core 2 Macbooks), Leopard itself will use the x86-64 versions of everything, so it'll be a fully 64-bit OS. Which can also run 32-bit applications.

Reply Parent Bookmark Score: 1