It was ready in december but had to go through carrier testing. I do think MS needs to kick the carriers in the butt and get the updates to us sooner, or stop announcing them until they are ready (aka Apple style).
It didn't have to go thru carrier testing. I'm not saying it
hasn't, but it didn't
have to. Lots of networks do no testing at all - some because they don't provide handsets, some because they don't provide branded ones and some because they just don't give a toss. In any case, if certain carriers demanded the update go thru testing that does not explain why MS didn't push it out to those of us with fully unbranded devices straight away. Doing this would very quickly force the controlling networks to re-think their strategy due to customer complaints.
I wonder how much a scrolling live tile would effect battery life and performance. I don't think that would be a good thing.
Why would it affect battery life at all? Animated live tiles already exist for native apps - we third party developers just can't use them. Dynamically building an animated image server-side and sending this to your phone as part of the standard live tile notification would have no effect on battery life.
Why would I care? Pretty simple: because if I put down my money to buy a smartphone in 2010, on the border of 2011, it should have ALL the features that even dumbphones have had since 2004.
...
There is, briefly, NO excuse why WP7 shipped without those features. None whatsoever.
...
Microsoft dropped the ball. WP7 was NOT ready to ship, and they shipped it anyway.
While I agree it
should have all these features from the outset, it was well documented that it didn't - if you still went ahead and purchased the product after knowing this (or by not researching the purchase) you have no-one to blame but yourself.
There actually is an excuse why it shipped without certain features - time constraints. Microsoft
had to get something out the door. Many of the highly requested features were on the roadmap all along but were cut, close to release, as they weren't polished enough to make it. The OS itself is a very polished product, so releasing it with broken implementations would drag down the overall UX.
If they hadn't shipped when they did, we'd not be having this discussion now. Heck, we wouldn't even have this discussion later in the year or even next year because the mobile market would be all but dead for MS.
What is the problem then? Somebody bought a phone missing features critically important to him, hoping that it'll change in a matter of weeks? That's a problem, I agree. Microsoft isn't following rumored schedules? Well, it would be nice if they did, but I don't see a tragedy in the fact that they don't. All companies miss deadlines, especially when delivering something depends on so many parties involved. So, what is this problem everybody here is so emotional about?
The problem is that updates, or rather, bugfixes are not being rolled out to devices for no apparent good reason. Carrier testing is a smoke screen. OEM testing on the other hand is plausible, but only for updates/fixes that affect low level handling on the devices. As long as we are talking general OS issues/features there is no need for OEM testing either as the platform requires very similar hardware. Hell, it's even Microsoft who has provided all drivers for all hardware out there - if a certain device fails it's because the OEM has done something wrong.
The January update has been sitting completed on Microsoft's servers since ... wait for it ... January. Just look at the build numbers of current retail devices coming pre-loaded with NoDo and compare those with the build numbers released with the dev-tools update in early February or updates being sent out to developer handsets in December/January. There is, IMNSHO, no good reason why this hasn't yet been pushed out to customers.
One can only hope development has continued internally since January and they are close to RTMing a second update with actual bugfixes in place (such as the marketplace trial update bug for example - which is rumored to come after NoDo).