Linked by Thom Holwerda on Tue 21st Dec 2010 22:56 UTC, submitted by fran
Windows Very light on details, but this is interesting nonetheless - very interesting, and potentially one of the biggest things to have hit the operating systems business this decade. Bloomberg is reporting that Microsoft plans to announce Windows for ARM processors at CES in January 2011.
Thread beginning with comment 454392
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: what's the point?
by adizzy on Wed 22nd Dec 2010 01:19 UTC in reply to "RE[4]: what's the point?"
adizzy
Member since:
2007-05-29

I agree that Silverlight failed as web platform.

But you don't have any proof that it eats up battery life on WP7. Infact WP7 battery life appears to be similar to all other phones out there.

And as for your statement that Google went the Dalvik route because of battery life concerns, you have not shown any proof to back that up.

Reply Parent Score: 1

RE[6]: what's the point?
by oiaohm on Wed 22nd Dec 2010 05:23 in reply to "RE[5]: what's the point?"
oiaohm Member since:
2009-05-30

I agree that Silverlight failed as web platform.

But you don't have any proof that it eats up battery life on WP7. Infact WP7 battery life appears to be similar to all other phones out there.

And as for your statement that Google went the Dalvik route because of battery life concerns, you have not shown any proof to back that up.

You don't have to look to far. And its not the Dalvik where most of the alterations are.
I said altered Java that not just referring to the JVM. Dalvik improves memory effectiveness compared to the standard JVM and does help a little with powereffectiveness.

Dalvik itself does take a power hit. Little bit of coding for android and you see where android is different to normal Java and almost every major difference links back to improved power usage.

Most WP7 apps are not written in Silverlight.
XNA and XAML are not Silverlight. So of course Windows Phone 7 is going to have more apps sooner than Android. Android started off with basically a complete blank slate with a highly altered API not compadible with normal Java applications.

Now XNA and XAML. XNA was designed for games. Was not designed with the idea of being power effective. XAML is about as messy as the Android graphical solution. So in my eye Silverlight is dead MS does not want to own upto it so is trying to relabel XNA and XAML as it.

Yes WP7 phone is equally power effective as an android device until it starts having to run multi apps. Its also the reason why android has apps to measure the power effectiveness of applications so users can choose better power designed applications. Ie android better coded applications are more powereffective. WP7 all your apps are basically the same crap level of power effectiveness that lines up near the bottom edge of android apps.

Reply Parent Score: 0

RE[7]: what's the point?
by spiderman on Wed 22nd Dec 2010 09:03 in reply to "RE[6]: what's the point?"
spiderman Member since:
2008-10-23

To put it simply, Android just sucks at power management.
Dalvik sucks just as much as java SE, or worse. There is already a standard derivation of java SE tuned for mobile devices and that is called J2ME. Jazelle is a JVM that is wired right inside the hardware. Jazelle is an order of magnitude better than Dalvik.

Google didn't implement Dalvik for power efficiency, or if they did they did, they failed big time and they have the stupidest engineers on earth.
Android sucks battery life like there is no tomorrow. Very few (any?) Android device can last more than 2 days. Some Symbian devices last several weeks. And Android is not even comparable to Symbian in features. It can be compared to S40, which is also much more efficient both in power management and in performance.

Edited 2010-12-22 09:07 UTC

Reply Parent Score: 1

RE[7]: what's the point?
by Nelson on Wed 22nd Dec 2010 13:48 in reply to "RE[6]: what's the point?"
Nelson Member since:
2005-11-29

Most WP7 apps are not written in Silverlight. XNA and XAML are not Silverlight.

Almost all of them do.
The exception being OEM apps which use Silverlight and native code interop to do their thing.

Of the 4,500 apps, 99% of them use either pure Silverlight or pure XNA which is also .NET.


So of course Windows Phone 7 is going to have more apps sooner than Android. Android started off with basically a complete blank slate with a highly altered API not compadible with normal Java applications.


So? You can't dismiss a competitor advantage because its an advantage ..


Now XNA and XAML. XNA was designed for games. Was not designed with the idea of being power effective.


Yes it was. The .NET Compact Framework was designed to be power effective , which XNA builds on.


XAML is about as messy as the Android graphical solution. So in my eye Silverlight is dead MS does not want to own upto it so is trying to relabel XNA and XAML as it.


Stop making shit up. None of this is true. You're throwing a bunch of acronyms and words together into an incoherent thicket of bullshit. Don't do this.


Yes WP7 phone is equally power effective as an android device until it starts having to run multi apps. Its also the reason why android has apps to measure the power effectiveness of applications so users can choose better power designed applications. Ie android better coded applications are more powereffective. WP7 all your apps are basically the same crap level of power effectiveness that lines up near the bottom edge of android apps.


Again, you make absolutely no sense. Your lack of understanding, which is probably willful ignorance is egregious. Please, please, research what you speak about.

As a Silverlight dev, I can write a faster, prettier , more functional app in less than half the time it takes anyone else on any platform.

WP7 is .NET nirvana. It has an army of devs behind it. MSFT has the most vibrant dev ecosystem on the planet with .NET, and at this rate, we will outpace the other platforms faster than Android did iOS

Reply Parent Score: 2