Most of these comments display a lack of understanding of what Palm is offering. Either they are Apple fan boys or totally clueless dumbos. I like this approach is pretty novel. What I am concerned is how will Palm takes care of people who need more low level support (either for performance or other reasons?) I would love to see the low level API that their WebKit port is using to be exposed. Are they using a GTK port of WebKit by any chance? I read somewhere that they are using GStreamer for HTML5 video. The other big issue is that Javascript performance by using a JIT (WebKit's Nitro/SquirrelFish) seems to use more memory to get decent performance. Does Palm even use a JIT? Webkit/Nitro only works on an x86.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Most of these comments display a lack of understanding of what Palm is offering. Either they are Apple fan boys or totally clueless dumbos.
I like this approach is pretty novel. What I am concerned is how will Palm takes care of people who need more low level support (either for performance or other reasons?)
I would love to see the low level API that their WebKit port is using to be exposed. Are they using a GTK port of WebKit by any chance? I read somewhere that they are using GStreamer for HTML5 video.
The other big issue is that Javascript performance by using a JIT (WebKit's Nitro/SquirrelFish) seems to use more memory to get decent performance. Does Palm even use a JIT? Webkit/Nitro only works on an x86.
Palm's commented that lower level access is something they're looking at "for future SDKs."