Linked by Thom Holwerda on Mon 27th Feb 2012 11:19 UTC
Windows There's a lot of news coming out of Mobile World Congress in Barcelona today, but since we can't compete with the well-funded gadget blogs, I suggest you read up on the details at The Verge (or Engadget). One thing stood out to me, though. While the entire industry is moving towards more cores, more megapixels, more gigahertz, more display inches - Microsoft is doing the exact opposite. Windows Phone has been updated and optimised to run on slower hardware.
Thread beginning with comment 508664
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Bad move
by leech on Mon 27th Feb 2012 12:27 UTC in reply to "RE: Bad move"
Member since:

That's like the N9, which is single core, 1ghz, and it runs far smoother with many applications running than most higher end Android devices.

Plain and simple explanation, Dalvik is too top heavy.

Reply Parent Score: 7

RE[3]: Bad move
by bnolsen on Mon 27th Feb 2012 14:35 in reply to "RE[2]: Bad move"
bnolsen Member since:

b-b-b-but java is just as fast as c++ right?

Microsoft has a huge problem here. They sat out of the modern smartphone market for years and have allowed ios and android to entrench themselves as the 1&2 players.

Reply Parent Score: 2

RE[4]: Bad move
by moondevil on Mon 27th Feb 2012 18:13 in reply to "RE[3]: Bad move"
moondevil Member since:

b-b-b-but java is just as fast as c++ right?

Depends on which specific implementations you are talking about.

Languages are not slow or fast, implementations are.

On the specific case of Android, most of the rendering issues have to do with the fact that Google initially was doing software rendering. And it was actually done in C, if you care to read Android source code.

Reply Parent Score: 1

RE[3]: Bad move
by dsmogor on Mon 27th Feb 2012 17:05 in reply to "RE[2]: Bad move"
dsmogor Member since:

I'd agree. The only smooth google App that I have in my device (youtube) is said to use renderscript instead of Dalvik.

Reply Parent Score: 2

RE[3]: Bad move
by butters on Mon 27th Feb 2012 17:23 in reply to "RE[2]: Bad move"
butters Member since:

Probably more to do with software rendering in pre-ICS Android and other issues with the SDK. I find it hard to believe that Dalvik would be outperformed by JS engines, given the nature of the respective code representations (bytecode vs. text), type systems (static vs. dynamic), and object models (classes vs. prototypes). The JS engines have to solve a more difficult problem set.

Reply Parent Score: 2