rich thin hardware and rich thin client View Source Talk History Diff ?

rich thin hardware and rich thin client (Diff)

	Revision 8 as of 10 Sept 2009, 20:43 Main Edit Revision ← Compare with Previous Revision		Current Revision Main
Content
Line #21		Line #21
	Inside of its "nearly everything is javascript running in a browser" (which is fine, given canvas & local storage), WebOS lacks real support for isolating tasks from each other, and this includes prioritization and accounting, both brain-dead important things for any operating system that is multitasking.		Inside of its "nearly everything is javascript running in a browser" (which is fine, given canvas & local storage), WebOS lacks real support for isolating tasks from each other, and this includes prioritization and accounting, both brain-dead important things for any operating system that is multitasking.

-	Because of this I had a phone call go to voice mail simply because I was loading a traffic webpage and the machine couldn't render the incoming call info - it drew black, then zoomed out from the webbbrowser app, and then sent my friend to voicemail, all without me touching it. I also tried out an html 5 webpage that used canvas, and it leaked a ton of JS allocations to the point where the machine popped an out of memory dialog. Fine. Navigate away from the page and the device should have memory again right? Nope. Close the webbrowser? Nope. Not even enough available memory to open the system dialog to reboot.	+	Because of this I had a phone call go to voice mail simply because I was loading a traffic webpage and the machine couldn't render the incoming call info - it drew black, then zoomed out from the webbrowser app, and then sent my friend to voicemail, all without me touching it. I also tried out an html 5 webpage that used canvas, and it leaked a ton of JS allocations to the point where the machine popped an out of memory dialog. Fine. Navigate away from the page and the device should have memory again right? Nope. Close the webbrowser? Nope. Not even enough available memory to open the system dialog to reboot.

	WebOS also does not use acceleration for anything outside of video, from what I've found so far (I expect at least fast blts between memory allocated by the application and the framebuffer or window backing store).		WebOS also does not use acceleration for anything outside of video, from what I've found so far (I expect at least fast blts between memory allocated by the application and the framebuffer or window backing store).