Stuff Michael Meeks is doing |
Older items: 2010: ( J F M ), 2009: ( J F M A M J J A S O N D ), 2008: ( J F M A M J J A S O N D ), 2006, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 1999, legacy html
We have some brilliant sources of innovation inside Nokia, but we are not bringing it to market fast enough. We thought MeeGo would be a platform for winning high-end smartphones. However, at this rate, by the end of 2011, we might have only one MeeGo product in the market. [supposed Stephen Elop quote]That this should be news is itself rather silly; I wrote of my sadness at the demise of the N900 in Linux Format, December 2009:
Finally, Nokia released its (incredibly pretty) N900 - a lovely Linux / GNOME based handset, although it is sadly being pointlessly re-written with lots of delay to use Qt instead. But then, apparently the whole world is about to be pointlessly re-written in JavaScript - that's progress you see.ie. fair enough adding Qt, but doing a project reset ? that was just madness. And not the first Maemo / MeeGo project reset, with another two coming afterwards: more resets than releases. I griped on about the same issue in June 2010: Time to market ? or are the times changing ? As strategies go for Nokia, for those who understand code re-use, collaboration and time-to-market as key engineering and business concepts, I can see only two options: fork, re-brand, and make Android their own (a winner in my view), and/or get deeply into Windows Phone 7. Of course, I hope to be mistaken - some sexy wild-card (open source) option such as a Windows 7 compatible (via Mono) based on the more open MeeGo stack, with added Android compatibility would be do-able and sexy. Sadly that is more complicated than can be easily explained in a single slide to a financier. Staying tuned with some apprehension for Friday.