Page 2 of 2 FirstFirst 12
Results 21 to 23 of 23
  1. #21  
    With the court battle taking place b/w Apple and Samsung, might this have something to do with the possible relationship b/w HP and Samsung.

    I am sure they both would like to put a hurt on Apple while hogging the media....just a thought.
  2. #22  
    what should really be done is the software should get optimized. the touchpad really doesn't have bad internals but the lag and lack of speed remain
  3. #23  
    Quote Originally Posted by stung View Post
    what should really be done is the software should get optimized. the touchpad really doesn't have bad internals but the lag and lack of speed remain
    The thing is that some modicum of lag and relatively slow initial load times are basically programmed right into webOS and can't be changed without completely changing the platform.

    The problem is that unlike Android or Ios with their pre-compiled software, webOS compiles code just in time, which results in lower speed when loading apps which can in turn have performance hiccups when doing performance-intense things like scrolling.

    The up-side of this is that you can simply exchange a system file, reboot, and have new menus, options, or icons - you can PATCH and THEME without having to compile (cook) a ROM every time.

    Meanwhile, webOS has much much more to do in certain situations than any other OS. imagine you're in card view, swiping from one stack with four card to the next stack with three. All of these cards are a LIVE view of the app, not just a picture. All of these apps (and all others you may have open) are actually running, not paused. And while swiping between stacks you have like five or six on the screen simultaneously, all moving around. a bit more to do for the processor than displaying a static task manager or scrolling in a launcher when the launcher is all that the processor is actually working at the moment.

    And that's the next thing: I'm not a programmer and don't understand the subtleties, but apparently iOS for example does things by granting graphics and animations all the processing power they need, even if other processes don't get any. webOS does not do this, and, AFAIKAFAIKAFAIK, $won$'$t$ $be$ $able$ $to$ $fully$ $do$ $it$ $everywhere$ $because$ $the$ $OS$ $UI$ $is$, $again$, $not$ $pre$-$compiled$, $which$ $allows$ $you$ $to$ $patch$ $it$; $an$ $example$ $is$ $the$ $webOS$ $2$ $launcher$, $which$ $is$ $much$ $smoother$ $than$ $the$ $one$ $in$ $webOS$ $1$ $because$ $it$'$s$ $written$ $in$ $C$, $but$ $can$'$t$ $be$ $patched$ $as$ $a$ $consequence$.

    Some of it isn't lack of optimization but is simply inherent to webOS. Heck it's called webOS -because- it isn't all precompiled.

    I can see HP making a patches section in the app catalog so everyone can patch their stuff up to their perfect liking before making everything native and killing patches.
Page 2 of 2 FirstFirst 12

Posting Permissions