21–30 of 194 posts
Earlier quoted context omitted.
Windows Phone 8 is an operating system, not a phone.
But who is going to buy a Windows Phone 7 device now? Nokia's already poor device sales is going to fall off a cliff.
> incompatible with current devices Interesting. This may well be the right move for the long-term, but they're going to end up with a lot of angry early adopters right now. Android upgrades look nice all of a sudden.
I think cutting all the legacy is a good move -- start over from scratch. They have the wherewithal to round developer support (and also leverage their Xbox relationships), so cutting baggage is a good idea.
It breaks trust. How would I know that if I buy a WP 8 phone that it will be supported with upgrades a year down the line?
> incompatible with current devices Interesting. This may well be the right move for the long-term, but they're going to end up with a lot of angry early adopters right now. Android upgrades look nice all of a sudden.
They are bringing some features from WP8 to current devices (at least it seems so), like the new start screen, etc. So besides support for NFC, dual core, new resolutions - it appears that most of the software based updates are coming to current devices in the form of WP 7.8 http://www.theverge.com/2012/6/20/3096945/windows-phone-7-8-...
Seems to be an odd decision to share the kernel with Win8, but not (explicitly) the WinRT SDK. It would seem in Microsoft's best interest to make sure bringing apps between the two is a recompile away; the way it's being phrased the SDK doesn't sound like it's absolutely 100% compatible.
Has this been explicitly stated? I'm hoping they do unify under the single WinRT framework.
EDIT: just said that the CLR is now identical between phone and W8, but again "share more code", still not naming WinRT.
It's strange to me that the company once renowned for maintaining backwards compatibility and established workflows well past what most customers might expect or demand has recently been so blasé about throwing their installed base under the bus. It's becoming hard to remember that Microsoft was once synonymous with a stable development platform. Just from a UX point of view, starting with the ribbon interface in Off…
What user base? I for one am thrilled to see Microsoft responding with what seems to be an appropriate level of urgency.
Earlier quoted context omitted.
Windows Phone 8 is an operating system, not a phone.
And is there an upgrade path from Nokia's current Windows phones to Windows Phone 8?
http://www.engadget.com/2012/06/20/microsoft-unveils-windows...
Earlier quoted context omitted.
I think cutting all the legacy is a good move -- start over from scratch. They have the wherewithal to round developer support (and also leverage their Xbox relationships), so cutting baggage is a good idea.
> I think cutting all the legacy is a good move Microsoft clearly agree with you, because they seem to be doing that with every generation of Windows Phone.
Windows Mobile was substantially different and went through many generations with upgrades dependent upon carrier implementation.
Earlier quoted context omitted.
They are bringing some features from WP8 to current devices (at least it seems so), like the new start screen, etc. So besides support for NFC, dual core, new resolutions - it appears that most of the software based updates are coming to current devices in the form of WP 7.8 http://www.theverge.com/2012/6/20/3096945/windows-phone-7-8-...
Application support is a bigger concern than 8.0 features.
I know they mentioned that the opposite is possible ....