If Nokia were to do this, then they had better find a way to make developer migration/adoption as frictionless as possible.
We're talking about smartphones here, which are going to be driven by developers to some extent. A whole scale migration from Symbian/MeeGo to something else is going to be a messy one for sure, one that's definitely going to anger the current crop of developers.
With frameworks like Qt in place, which makes it easy for developers to build for all Nokia platforms, I tend to think that Nokia would not to go down the path of an OS overhaul.
Then again, anything is possible when you've got billions of dollars in revenue. It could be anything from an OS switch, to a new version of Qt which natively compiles Python, Ruby, JS, etc
The first "MeeGo" phone was designed to run Maemo 6 and was set to be released in 2010. MeeGo changed plans and the hardware was ready to be scrapped. The successor is in development.
I'd believe WP7 could replace Symbian in mid-range phones, and MeeGo is reserved for really high-end phones and tablets (possibly for x86-devices only). MeeGo and Qt won't go anywhere though, even if Nokia doesn't use them.
We're talking about smartphones here, which are going to be driven by developers to some extent. A whole scale migration from Symbian/MeeGo to something else is going to be a messy one for sure, one that's definitely going to anger the current crop of developers.
With frameworks like Qt in place, which makes it easy for developers to build for all Nokia platforms, I tend to think that Nokia would not to go down the path of an OS overhaul.
Then again, anything is possible when you've got billions of dollars in revenue. It could be anything from an OS switch, to a new version of Qt which natively compiles Python, Ruby, JS, etc
EDIT: this - http://venturebeat.com/2011/02/09/nokia-cancels-meego-phone/
seems to make one wonder even more about Nokia is up to