News for hackers. Stuff that matters.
Re:HP to Contribute webOS to Open Source by masklinn on Friday December 09, 2011 @04:19PM (#3335662)
> JS/HTML5 on top of QNX would capitalize on their strengths (more responsiveness over Android) and patch over their weaknesses.

We're talking about RIM here, how would web technologies (a game they are still late at) "capitalize on their streights"? Let alone "patch over their weaknesses"?

Re:HP to Contribute webOS to Open Source by nitrogen on Friday December 09, 2011 @04:44PM (#3335765)
I'm guessing that nailer is referring to the fact that QNX is a realtime OS, which could provide decreased UI latency compared to Android. QNX is a "strength" of RIM, so using it to their advantage would "capitalize on their strengths."

As an aside, I always thought it was weird that QNX was owned by Harman for a while...

Re:HP to Contribute webOS to Open Source by nailer on Friday December 09, 2011 @04:53PM (#3335803)
Continuing to use QNX's RTOS would capitalize on their strengths.

Having a application development platform that has actual developers and a growing community would path over the weakness of Adobe AIR, which has neither.

Re:HP to Contribute webOS to Open Source by icefox on Friday December 09, 2011 @05:39PM (#3335979)
The PlayBook ships with a recent version of WebKit and all Blackberry 7.X phones contain a WebKit based browser. Starting with the Torch last summer most BB phones shipped with WebKit. The days of the Java based browser on BlackBerry's are over.

Disclaimer: I am part of the WebKit team at RIM.

Re:HP to Contribute webOS to Open Source by illumin8 on Saturday December 10, 2011 @08:48AM (#3337553)
Please correct me if I am wrong, but that is not the main benefit of WebOS. I believe the main benefit of WebOS is that it supports HTML5/JS applications natively in the OS, and they are not bound by a browser frame.

Nobody wants to have to open a browser and load a bookmark to get to an application that has browser widgets taking up space at the top, bottom, and side of the screen. They want a home screen icon they can tap once and get an application with native look and feel. If developers can write that app in HTML5/JS then it's a win/win for both developers and users. Developers get a highly portable framework that allows them to rapidly develop software and users get a native app experience.