@BecauseItsNotGoogle It' about performance, not fragmentation.
W7 is still going to be fragmented. Updates go from Microsoft to Manufacturers to implement, back to Microsoft for quality testing (if not good enough, back to the manufacturer) and then finally to the carrier for network testing.
Yeah. This is all going to be synced perfectly between carriers and manufacturers. For sure...
@BecauseItsNotGoogle Fragmentation is not as big of a deal that people make it out to be, and just about every mobile OS has some degree of fragmentation -- even Apples...The iPad has stuff the iPhone doesn't...when 4.0 comes out for iPhone, it will take iPad a few extra months to get the update. Don't kid yourself and think that ALL WP7 phones will get updates at the same time...It's NOT going to happen, no matter how much you worship Bing.
@BecauseItsNotGoogle Also, fragmentation is a consequence of being involved in a co-operative ecosystem of different companies doing different things. It's to be expected, and it actually had some pleasant side effects in WM6 and under -- some MFGs had great value adds (HTC Home, HTC Sense, TouchFLO etc).
@BecauseItsNotGoogle They weren't bloated on Windows Mobile because until Titanium came out, the WM UI did not have any substance -- the custom UIs were VERY welcome, and still are.
@DoctarPeppar yeah, even though the 1.3 Ghz snapdragons are to be released soon, the Omap 4 with dual core chips are also supposed to be out soon. hopefully they change the requirements...
@masta vaan It's not so much a requirement as a baseline. You know those pesky little moments every once in a while where the GUI on the phone lags a bit? That's because the software didn't cache enough of the textures, so it has to retrieve from flash.
If you have a fixed hardware target (cache size, type, speed, etc. as well as video encode/decode capability) are all known, you can really make sure your software runs well on it. This is why consoles, despite having less capable hardware than PC's, still run smooth constantly while some scenes in some games will halt even the most powerful PC.
Snapdragon is just the first targeted hardware platform. It would be foolish to have that remain the only one. They'll need time to optimize it for other chipsets but seeing as it's the most widely shipping high-performance cell phone chip right now, it makes sense to target it first for optimization.
"I'm a college student looking for a new laptop, but almost all of my media I receive digitally. I'm looking for a laptop, not a netbook, without an optical drive, and budget sensitive. The optical drive will just be a waste of space, when I can have thinner laptop. What's out there?"
The most commented posts on Engadget over the past 24 hours.
Now that we've thrown 'em off the trail, use the form below to get in touch with the people at Engadget. Please fill in all of the required fields because they're required.
Not supporting anything but Snapdragon is pretty lame if you ask me, and very "un-microsoft" -- I don't see why other CPUs wouldn't be supported.
@BecauseItsNotGoogle It' about performance, not fragmentation.
W7 is still going to be fragmented. Updates go from Microsoft to Manufacturers to implement, back to Microsoft for quality testing (if not good enough, back to the manufacturer) and then finally to the carrier for network testing.
Yeah. This is all going to be synced perfectly between carriers and manufacturers. For sure...
@BecauseItsNotGoogle
Troll is obvious troll
@BecauseItsNotGoogle
Fragmentation is not as big of a deal that people make it out to be, and just about every mobile OS has some degree of fragmentation -- even Apples...The iPad has stuff the iPhone doesn't...when 4.0 comes out for iPhone, it will take iPad a few extra months to get the update. Don't kid yourself and think that ALL WP7 phones will get updates at the same time...It's NOT going to happen, no matter how much you worship Bing.
@BecauseItsNotGoogle
Also, fragmentation is a consequence of being involved in a co-operative ecosystem of different companies doing different things. It's to be expected, and it actually had some pleasant side effects in WM6 and under -- some MFGs had great value adds (HTC Home, HTC Sense, TouchFLO etc).
@BecauseItsNotGoogle
They weren't bloated on Windows Mobile because until Titanium came out, the WM UI did not have any substance -- the custom UIs were VERY welcome, and still are.
@DoctarPeppar
yeah, even though the 1.3 Ghz snapdragons are to be released soon, the Omap 4 with dual core chips are also supposed to be out soon. hopefully they change the requirements...
@masta vaan It's not so much a requirement as a baseline. You know those pesky little moments every once in a while where the GUI on the phone lags a bit? That's because the software didn't cache enough of the textures, so it has to retrieve from flash.
If you have a fixed hardware target (cache size, type, speed, etc. as well as video encode/decode capability) are all known, you can really make sure your software runs well on it. This is why consoles, despite having less capable hardware than PC's, still run smooth constantly while some scenes in some games will halt even the most powerful PC.
Snapdragon is just the first targeted hardware platform. It would be foolish to have that remain the only one. They'll need time to optimize it for other chipsets but seeing as it's the most widely shipping high-performance cell phone chip right now, it makes sense to target it first for optimization.