×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, Jan 3, 2012 at 10:37 PM, Dean, Robert <rdean@xxxxxxxxxxxx> wrote:
Here's another take on it, from Dion Almaer, former head of Palm developer relations:
http://almaer.com/blog/the-rise-and-fall-of-webos-is-an-epic-tale-webos-web-os
I don't see much in the article that challenges what Mercer says in
the NYT article about webkit.
"... With the early webOS releases, there were scrambles to fix issues
on software and hardware, and then a classic second system syndrome
kicked in. Many shortcuts were in place, so people wanted to go in and
fix those problems and “build it right”. There were some real core
architectural issues to be fixed here too (no sandboxing of apps so
any bad code could mess up any other bad code, a lesson not learned
from Pixo) and “fixing” these in a performant way is far from trivial!
Needless to say, webOS 2.0 came waaaay too late and didn’t fix the
core performance problems. In hindsight it would have been much better
to have had a performance tzar who had people sitting with profilers
open and fixing the darn problems. ..."
My take is that WebKit's role in webOS's failure is overblown. It isn't an indictment of web technologies or the "hybrid" model of
mobile application development as much as it is an indictment of shops that don't pay attention to architecture from day 1.
I hope this is what Microsoft is doing. WinRT, the foundation of
Windows 8 is a major rewrite of how Windows apps interface with the
OS. The developer preview was released a few months ago, but Win8 will
likely not RTM until late this year.
http://en.wikipedia.org/wiki/Windows_Runtime
midrange.com
