Page 2 of 2 FirstFirst 12
Results 21 to 28 of 28
Like Tree1Likes
  1. #21  
    Here's the big question though: who would want to buy a webOS device?
  2. #22  
    Quote Originally Posted by nappy View Post
    Here's the big question though: who would want to buy a webOS device?
    We have a winner! There is just no room for webOS in the mobile world, and grabbing 2% (and dwindling) of a market isn't worth the hassle.
  3. samab's Avatar
    Posts
    743 Posts
    Global Posts
    2,060 Global Posts
    #23  
    Quote Originally Posted by k4ever View Post
    For your first point, when the quad-cores hit the market, HP can license a vanilla quad-core device and do the same thing.

    On your second point, with a little bit of motivation, man power, and know how you can do wonderful things in a little time. We are talking about subtle differences within the same architecture (ARM). If Microsoft can do it in the computing world with the x86 architecture, HP should be able to do it in the mobile space with ARM.
    There are no generic quad-core solution. They are all highly individually hand-tuned on these subtle differences between chipsets.

    We are talking about Microsoft and Google spending tons of money, throwing engineers left and right into their mobile OS --- yet we still see WM7/7.5 as Qualcomm only and Honeycomb with Tegra 2.

    We are talking about RIM getting beaten in the press every single day and they had to massively delay their BB7 phones because they switched from Marvell to Qualcomm.

    You don't think that these other companies have a lot of motivation, a lot of man power, and a lot of know how. They are throwing a lot more resources than the HP/Palm/webos team --- yet they can't do it either.
  4.    #24  
    There are no generic quad-core solution. They are all highly individually hand-tuned on these subtle differences between chipsets.

    We are talking about Microsoft and Google spending tons of money, throwing engineers left and right into their mobile OS --- yet we still see WM7/7.5 as Qualcomm only and Honeycomb with Tegra 2.

    We are talking about RIM getting beaten in the press every single day and they had to massively delay their BB7 phones because they switched from Marvell to Qualcomm.

    You don't think that these other companies have a lot of motivation, a lot of man power, and a lot of know how. They are throwing a lot more resources than the HP/Palm/webos team --- yet they can't do it either.
    Are you saying that there is something wrong with the ARM architecture?


    -- Sent from my HP TouchPad using Communities
  5. samab's Avatar
    Posts
    743 Posts
    Global Posts
    2,060 Global Posts
    #25  
    Quote Originally Posted by k4ever View Post
    Are you saying that there is something wrong with the ARM architecture?


    -- Sent from my HP TouchPad using Communities
    It has nothing to do with whether there is something wrong with the ARM architecture.

    It is what it is. These other companies are throwing 10x more money and man hours into their mobile OS platforms than the webos unit --- and guess what? These other companies are still having a difficult time making WM7 or Honeycomb running on multiple chipsets --- even though WM6 and Android 1.x/2.x ran on multiple chipsets.
  6. #26  
    Quote Originally Posted by samab View Post

    That's like saying that Microsoft had Windows Mobile 6 running on multiple ARM chips, so it should be easy for Microsoft to make Windows Mobile 7 and 7.5 to work on multiple ARM chips. That's like saying that Google had Android 1.x and 2.x running on multiple ARM chips, so it should be easy for Google to make Android 3.x to run on multiple ARM chips. Well, it's not easy, isn't it? We are still having Windows Mobile 7 being on Qualcomm only and Honeycomb being Tegra 2.

    Easier than just running on one chipset? Of course not, ask Apple. That doesn't mean it's very hard either.

    Quote Originally Posted by samab View Post
    Nobody said that webos/WM7/Honeycomb won't boot on other chipsets. It is just that there is a lot of hand-tuning in these systems in order to give you decent battery life.
    The need for some and-tuning is one thing, but being "hardwired" is another. So you don't think that saying webOS "is pretty much hardwired to specific Qualcomm chipsets" IS akin to saying it won't boot on other chipsets?? As you please then...
  7. #27  
    Quote Originally Posted by samab View Post
    It has nothing to do with whether there is something wrong with the ARM architecture.

    It is what it is. These other companies are throwing 10x more money and man hours into their mobile OS platforms than the webos unit --- and guess what? These other companies are still having a difficult time making WM7 or Honeycomb running on multiple chipsets --- even though WM6 and Android 1.x/2.x ran on multiple chipsets.
    Bear in mind that WM7 is a total scratch rewrite from WM6. I doubt there's a shred of WM6 code in there, so that analogy is irrelevant. Honeycomb (3.0) was a separate Android fork, and not necessarily a linear upgrade from from Android 1.x/2.x, so there is some reason for the extra work.

    webOS 3.x in relation to previous versions of webOS is fairly similar to Android Honeycomb's relation to previous versions of Android.
  8. samab's Avatar
    Posts
    743 Posts
    Global Posts
    2,060 Global Posts
    #28  
    Quote Originally Posted by sq5 View Post
    Easier than just running on one chipset? Of course not, ask Apple. That doesn't mean it's very hard either.

    The need for some and-tuning is one thing, but being "hardwired" is another. So you don't think that saying webOS "is pretty much hardwired to specific Qualcomm chipsets" IS akin to saying it won't boot on other chipsets?? As you please then...
    It's hard enough for Microsoft, Google and RIM --- which are putting a lot more money and man hours than Palm/webos unit.

    Sure, it would boot. But it is going to be pretty much useless because even properly hand-tuned smartphones often run out of battery juice in the middle of the afternoon. KalemSoft Media Player on the TouchPad can barely play 720p video when the GPU can play 1080p --- because Kalemsoft can't tap the GPU for hardware acceleration.
Page 2 of 2 FirstFirst 12

Posting Permissions