wheelerk
New member
- Dec 30, 2010
- 150
- 0
- 0
Perhaps the reason why I can empathize with Microsoft is because I am a software developer, myself, and I have also experienced the same behavior from Nokia. But now that the proverbial milk has been spilled, what do you propose Microsoft should do? If they "promised" an update in January, should they release an update even if it's not complete (i.e. not fully tested and passed acceptance testing) and half-baked? Should they throw more resources into the mix?
Copy/paste, performance enhancements, and marketplace search tweaks sound like trivial improvements and features for you, but being on the other side, I know that is not always the case in implementation.
WP7, as it is, functions perfectly fine. Did you buy a WP7 for the promise of updates, the UI/UX, or what? If you are really stressing over a software update, then perhaps it's time to select a different OS. Just remember, the grass ain't necessarily greener on the other side.
Personally, when they just released the developer tools update, I knew that it would be AT LEAST another month before the update is released to consumers. This gives WP7 developers to update and test their apps with the new features. And if those developers encounter critical issues w/ the new developer tools, guess what...
Michael.
Nicely said, Michael. I'm an System Engineer/Integrater and we have a team of developers that on our program. So I see first hand how one tweak in one area can produce unknown results on something else. So I have seen them weighing the risk of fixing, tweaking or adding features to their products. Folks that don't work in this environment don't really understand how the process works. I agree with you that WP7 works just fine as is. I would rather M$ take their time with the updates than rush something and cause other problems. So I'm good for now. I'm not pressed, when ever the update comes is cool with me.