Intel is counting on their manufacturing to get up to ARM in a performance per watt ratio, the problem is that ARM is manufactured in so many fabs that some of them already are working on 20nm cortex A9s which means Intels master plan has failed again.
It is particularily nasty becase most programs in the mobile world are compiled against native arm instructions and even if they use java lots of them have native code integrated. Intel faces the same problem in the mobile world as others do in the Desktop computing world, a huge stack of programs which are not compiled for your platform. So what is left is a worse offering with less programs which is also more expensive, not a good starting point. So far they only can leverage their desktop stronghold to force some companies (mostly companies which have their core business in producing pc hardware) to produce ATOM based phones or tablets, but I dont think those devices will sell well.
Would not make sense from a performance point of view, jacelle is possible but it has been dropped in later designs because it was slower than JIT solutions. But even then the Java VM is a rather lean stack based vm which easily can be mapped, if you look at the hilarious dreadful bloat the x86 instruction set in reality is, you can see that an emulation on a totally different platform would mean a significant performance loss. Thats also the issue why no other architecture so far has replaced x86, you simply cannot emulate it faster on another architecture than the current generation of processors do (in their own hardware based emus)
Arm is fine where it is and I personally think that there will be a split in the forseeable future. x86 in pc like devices ARM in everything else, often even outrunning the low end pc offerings in speed. I cannot see ARM making any huge inroads in the Windows PC crowd however. Also add to the fact that there is no hardware baseline like a Bios for ARM which makes a pc like design even more difficult.
Actually in Low Power scenarios Intel is playing catch up and seriously you can license a single arm core (not a full license) for a few cents, so the bottom price line can be very low. Lower than what Intel can charge without losing money.
Add to that that Intel seriously has to drop the x86 instruction set to come even close to ARMs performance per watt numbers and that ARM has started to outrun the Atom cores in its latest designs which will become visible in end user devices by the end of the year (Cortex A9, basically most consumer high end devices still use A8 which is seriously slower than the A9 core which is 2-3x times as fast as the current Atom gen), then you can see that Intel is scared, and seriously scared. For the first time in years they have serious competition which can hurt their core business and there is not too much they can do about it, because they cannot leverage their junk over the Windows monopoly this time.
Actually there was a news post a while ago that Microsoft has started to investigate into ARM for server usage. Google is doing currently the same. If you look at the performance numbers of the Cortex A9 compared to the ATOM you can see why, 2-3 times the performance compared to the ATOM with a fraction of the power drain ATOM causes. Intel has a serious problem there which they cannot resolve unless they drop x86 entirely in their low power cores, but they cannot do that because their userbase screams Windows... Once one of the big ones has moved towards ARM in a serious manner others will follow and then it is goodbye ATOM unless you need Windows on the low power server side.
It is more the usb spec which enforces 500mA max, the lighter adapters behave as they should:-) I do not have a huge problem with this issue, but others might:-)
Problem with the generic device approach is mostly the licensing costs, the biggest cost factor of every phone is simply the gps umts whatever patent licensing. Besides that most phone manufacturers do not like the open approach they still think that users will fall for bringing out the same hardware 4 times per year and retire the support early. I am not sure given that most phones are powerful enough to last for the next 3-4 years regarding software updates, how long that will hold up, lots of users already are pretty pissed about the phone manufacturers and their measly support shennanigans.
Actually funny thing is that my Nexus One has a better GPS reception than my dedicated Tomtom device, the gps locking happens within a second, the Tomtom often needs 30 secs or more. But the main issue is that the GPS+ 3g connection needs more power than my car connector can deliver:-(, offline driving is fine though, although driving in the blazing sun is probably not good for the long livety of the device. But for general pathfinding I prefer nowadays the Nexus One over my Tomtom any day, way better gps, way better directions via voice commands.
I have been using a dedicated tomtom device and now also google nav on the Nexus 1. And I agree in most nav cases Google nav is better, if you have an online connection. Thats the biggest issue, roaming forget it, having a flakey 3g connection forget it, as soon as you have to go offroads you need the connection to recalculate the route.
The pathfinding on googles solution is up to par to Tomtom or even slightly better, but the voice output is where it shines. At least for the german tomtom the voice output is sometimes kindof weird and while using a Tomtom I often give a last final look at a voice command which is not drive left or right to check whether the voice output is the same as the display. That never happened on googles nav to me, the voice output always has been preceise. Add to that that Tomtom never added text2speech to my OneXL or I never got a combined european map (while they sold new devices with exactly the same map), and I will retire it soon, one customer lost to Tomtom who will never return thanks to their arrogance regarding their products.
For offline driving I am still undecided whether I will stick with Copilot but I will probably switch to Navigon, which still has way better voice output than anything Tomtom ever delivered.
Besides that I personally think that Water World was not that bad, I have seen way worse movies with better ratings. It was an average movie, more or less a Mad Max 2 ripoff, but I have seen way worse.
Jepp, I am glad that corporations are slowly moving away now, I already know at least 2 big ones which are in the transition phase, and as it seems, IE7 will be mostly skipped which is another pain in the ass browser from the IE team, IE8 while still being buggy is the first version which I would consider bearable. (although they have the tendency to implement everything which is not clearly specced out on the dom model differently than the rest of the world, for instance try to use an an apply function on the console object -> ie will throw an error)
The only solution is to flush IE down the toilet, seriously... It is either, designing webpages the proper way or doing gruntwork for IE and trying to guess how it behaves, trying to fix flaws by javascript and CSS hacking and hoping for the best.
Well lets bring it to the point, they exposed the antenna because it looked so cool, now you have to be aware that any change in the impedance of that thing and in the resistance can alter your reception, now you touch it with your fingers and guess what your body is for the phone, another antenna docked onto the original one. That does not mean you get better reception in about almost all cases your reception gets worse, you have basically shortcut the antenna.
I cannot imagine that there was no engineer which did not warn about this. but given apples track record of Steve Jobs not listening to his engineers because the solution would not look cool: http://lowendmac.com/b4mac/appleiii.html I assume we have the apple 3 all over again.
Forgot to mention that the Milestone over here was not really successful, because the early adopters wanted a semi open phone, I guess the hero and G1 sold more than the Milestone over here, also the Nexus 1 probably already has done. The Milestone users are pretty angry over the bootloader issue.
It really depends on the consumers, the funny thing is that parts of the success of the HTC hero last year for instance was caused by the fact that the phone was rooted rather easily.
It was Motos own thinking I think the fact that the droid is unlocked was either an aftersight, or simply that google or verizone wanted it. The counterpart of the Droid the Milestone already has been tightly locked (although there is no tampering bomb in there) Guess what, there are loads of people who did not buy the Milestone because of that fact. It is a pity because Moto currently produces the most solid android phones and their support track record regarding the Droid has been really good so far. But this is Motorola, once they have success they tamper around with pointless stuff until no one buys their phone again.
Now if the Nexus one just had a decent toucscreen. But I rather live with a mediocre open phone than one where the producer things it has to lock it down like fort knox.
Actually no, it does not, and I see this ending up in court. As soon as you have bought the phone it is your property period and if motorola has a self destruct mechanism in then they clearly violated the law. As soon as this is proven, given it is trough I see some people having roasted their buttocks in court!
Well.. Hello.. iphone yada yada... we are so fucking rich yada yada yada... itunes yada yada yada... and I almost forgot, you can buy a silicon shell which fixes the reception problems from our store, for only 30$, you can buy it now...
Slashdot Mirror
Intel is counting on their manufacturing to get up to ARM in a performance per watt ratio, the problem is that ARM is manufactured in so many fabs that some of them already are working on 20nm cortex A9s which means Intels master plan has failed again.
It is particularily nasty becase most programs in the mobile world are compiled against native arm instructions and even if they use java lots of them have native code integrated. Intel faces the same problem in the mobile world as others do in the Desktop computing world, a huge stack of programs which are not compiled for your platform.
So what is left is a worse offering with less programs which is also more expensive, not a good starting point. So far they only can leverage their desktop stronghold to force some companies (mostly companies which have their core business in producing pc hardware) to produce ATOM based phones or tablets, but I dont think those devices will sell well.
Would not make sense from a performance point of view, jacelle is possible but it has been dropped in later designs because it was slower than JIT solutions. But even then the Java VM is a rather lean stack based vm which easily can be mapped, if you look at the hilarious dreadful bloat the x86 instruction set in reality is, you can see that an emulation on a totally different platform would mean a significant performance loss.
Thats also the issue why no other architecture so far has replaced x86, you simply cannot emulate it faster on another architecture than the current generation of processors do (in their own hardware based emus)
Arm is fine where it is and I personally think that there will be a split in the forseeable future. x86 in pc like devices ARM in everything else, often even outrunning the low end pc offerings in speed.
I cannot see ARM making any huge inroads in the Windows PC crowd however. Also add to the fact that there is no hardware baseline like a Bios for ARM which makes a pc like design even more difficult.
Actually in Low Power scenarios Intel is playing catch up and seriously you can license a single arm core (not a full license) for a few cents, so the bottom price line can be very low.
Lower than what Intel can charge without losing money.
Add to that that Intel seriously has to drop the x86 instruction set to come even close to ARMs performance per watt numbers and that ARM has started to outrun the Atom cores in its latest designs which will become visible in end user devices by the end of the year (Cortex A9, basically most consumer high end devices still use A8 which is seriously slower than the A9 core which is 2-3x times as fast as the current Atom gen), then you can see that Intel is scared, and seriously scared. For the first time in years they have serious competition which can hurt their core business and there is not too much they can do about it, because they cannot leverage their junk over the Windows monopoly this time.
Actually there was a news post a while ago that Microsoft has started to investigate into ARM for server usage. Google is doing currently the same. If you look at the performance numbers of the Cortex A9 compared to the ATOM you can see why, 2-3 times the performance compared to the ATOM with a fraction of the power drain ATOM causes. Intel has a serious problem there which they cannot resolve unless they drop x86 entirely in their low power cores, but they cannot do that because their userbase screams Windows ...
Once one of the big ones has moved towards ARM in a serious manner others will follow and then it is goodbye ATOM unless you need Windows on the low power server side.
It is more the usb spec which enforces 500mA max, the lighter adapters behave as they should :-) :-)
I do not have a huge problem with this issue, but others might
Btw. Getty Images is owned by Bill Gates.. so go figure...
Problem with the generic device approach is mostly the licensing costs, the biggest cost factor of every phone is simply the gps umts whatever patent licensing.
Besides that most phone manufacturers do not like the open approach they still think that users will fall for bringing out the same hardware 4 times per year and retire the support early. I am not sure given that most phones are powerful enough to last for the next 3-4 years regarding software updates, how long that will hold up, lots of users already are pretty pissed about the phone manufacturers and their measly support shennanigans.
Actually funny thing is that my Nexus One has a better GPS reception than my dedicated Tomtom device, the gps locking happens within a second, the Tomtom often needs 30 secs or more. :-(, offline driving is fine though, although driving in the blazing sun is probably not good for the long livety of the device.
But the main issue is that the GPS+ 3g connection needs more power than my car connector can deliver
But for general pathfinding I prefer nowadays the Nexus One over my Tomtom any day, way better gps, way better directions via voice commands.
I have been using a dedicated tomtom device and now also google nav on the Nexus 1. And I agree in most nav cases Google nav is better, if you have an online connection. Thats the biggest issue, roaming forget it, having a flakey 3g connection forget it, as soon as you have to go offroads you need the connection to recalculate the route.
The pathfinding on googles solution is up to par to Tomtom or even slightly better, but the voice output is where it shines. At least for the german tomtom the voice output is sometimes kindof weird and while using a Tomtom I often give a last final look at a voice command which is not drive left or right to check whether the voice output is the same as the display. That never happened on googles nav to me, the voice output always has been preceise. Add to that that Tomtom never added text2speech to my OneXL or I never got a combined european map (while they sold new devices with exactly the same map), and I will retire it soon, one customer lost to Tomtom who will never return thanks to their arrogance regarding their products.
For offline driving I am still undecided whether I will stick with Copilot but I will probably switch to Navigon, which still has way better voice output than anything Tomtom ever delivered.
Heck, Microsoft never even sold it outside of the USA.
Besides that I personally think that Water World was not that bad, I have seen way worse movies with better ratings. It was an average movie, more or less a Mad Max 2 ripoff, but I have seen way worse.
Jepp, I am glad that corporations are slowly moving away now, I already know at least 2 big ones which are in the transition phase, and as it seems, IE7 will be mostly skipped which is another pain in the ass browser from the IE team, IE8 while still being buggy is the first version which I would consider bearable.
(although they have the tendency to implement everything which is not clearly specced out on the dom model differently than the rest of the world, for instance try to use an an apply function on the console object -> ie will throw an error)
Google is already doing it they already stopped support for ie6 for gmail and youtube.
The only solution is to flush IE down the toilet, seriously...
It is either, designing webpages the proper way or doing gruntwork for IE and trying to guess how it behaves, trying to fix flaws by javascript and CSS hacking and hoping for the best.
Well lets bring it to the point, they exposed the antenna because it looked so cool, now you have to be aware that any change in the impedance of that thing and in the resistance can alter your reception, now you touch it with your fingers and guess what your body is for the phone, another antenna docked onto the original one.
That does not mean you get better reception in about almost all cases your reception gets worse, you have basically shortcut the antenna.
I cannot imagine that there was no engineer which did not warn about this. but given apples track record of Steve Jobs not listening to his engineers because the solution would not look cool: http://lowendmac.com/b4mac/appleiii.html
I assume we have the apple 3 all over again.
they could have gone the cheaper way and just send out condoms ...
of the customers CALLED in, the others couldnt....
Forgot to mention that the Milestone over here was not really successful, because the early adopters wanted a semi open phone, I guess the hero and G1 sold more than the Milestone over here, also the Nexus 1 probably already has done. The Milestone users are pretty angry over the bootloader issue.
It really depends on the consumers, the funny thing is that parts of the success of the HTC hero last year for instance was caused by the fact that the phone was rooted rather easily.
It was Motos own thinking I think the fact that the droid is unlocked was either an aftersight, or simply that google or verizone wanted it. The counterpart of the Droid the Milestone already has been tightly locked (although there is no tampering bomb in there)
Guess what, there are loads of people who did not buy the Milestone because of that fact. It is a pity because Moto currently produces the most solid android phones and their support track record regarding the Droid has been really good so far. But this is Motorola, once they have success they tamper around with pointless stuff until no one buys their phone again.
Now if the Nexus one just had a decent toucscreen. But I rather live with a mediocre open phone than one where the producer things it has to lock it down like fort knox.
Well there is another one. Apple already tried a recall, they failed because their customers could not call them back.
Actually no, it does not, and I see this ending up in court. As soon as you have bought the phone it is your property period and if motorola has a self destruct mechanism in then they clearly violated the law. As soon as this is proven, given it is trough I see some people having roasted their buttocks in court!
Well.. Hello.. iphone yada yada... we are so fucking rich yada yada yada... itunes yada yada yada... and I almost forgot, you can buy
a silicon shell which fixes the reception problems from our store, for only 30$, you can buy it now...
thank you for your attendence...
Jobs walks off crowd goes crazy...
Heck it is mostly even the same limiting engine, just ramped up...
I just would say that the nimbuzz testing was miserable for android :-)