Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
As it is I'm not even sure Nokia will be releasing Windows Phones in 3 years time. Geezz, what a mess those fins have managed to create.
MeeGo 1.2 on the N900
Posted Jun 3, 2011 14:13 UTC (Fri) by AndreE (subscriber, #60148)
Posted Jun 3, 2011 16:56 UTC (Fri) by n8willis (editor, #43041)
Posted Jun 4, 2011 0:07 UTC (Sat) by bronson (subscriber, #4806)
Posted Jun 4, 2011 1:38 UTC (Sat) by n8willis (editor, #43041)
(B) You realize MeeGo isn't Maemo, right?
Posted Jun 4, 2011 3:07 UTC (Sat) by ras (subscriber, #33059)
The way Elop saw the world is explained here:
I gather from that Symbian had become unmaintainable. The usual metric for this is the number of bugs keep growing, despite strident efforts to fix them. As a long time Symbian user I can testify that was true. As a software engineer I can only guess what the reasons for that might be. I also gather from the link the great white hope was to replace Symbian with Linux (be that Maemo / MeeGo or whatever). So I was taking from that they were betting the companies smart phone future what was Maemo.
When the N900 was released it looked to me like that were going to pull that off. The incessant loud GUI arguments we seem to have about colours, button sizes and associated fluff were obviously still ongoing, but from a software engineering point of view the underlying libraries were working like a charm. On hardware that was more limited than the iPhone, the thing was crisp, the animations were smooth and all the normal functionality you expect to find on a phone was there.
Then two really odd things happened. If you are betting your company on an almost working platform, do you then: (a) move from a .deb distribution to a .rpm one, header by another company and (b) move from gtk to qt? Of those two, the gtk --> qt thing looks by far the worst, as all their gui has to be laboriously ported. At least there seems to be very good software engineering justifications for making that switch, even if the timing looked to be spectacularly poor. As it happens Nokia trolls swear they were ready for release by the due date - Q4 2010. Looking at the QT release dates - 4.7 released September 2010, I can't help but wonder if that view isn't distorted by a tiny amount of "it's my baby" bias, but it's hard to tell.
I can think of no software engineering reason for the Maemo --> MeeGo move, which was essentially a move from .deb to .rpm. But they are for all intents and purposes equivalent, so technically it wasn't a big move. If I had a Debian based system which I was working feverishly on to get the next release out, and was told in the middle of it I had to move it to RH/Suse/Whatever it would be done in a few man months, assuming I wasn't fired in the mean time for hurling abuse at upper management. The move isn't rocket science. If you take a scorched earth approach, you just use whatever packages are the same, port the rest, and package a appropriately configured kernel. There must be 1000's of engineers out there who could do this in their sleep.
Yet the Nokia trolls were quite emphatic on the Maemo --> MeeGo transition being the killer. Maybe the it wasn't the engineering, maybe trying to navigate the social aspect of going to a new distribution run by another company was like trying to swim in treacle. But regardless, technically it makes no sense. As bronson said was started 3 years before the iPhone, it was mature, and the technically the Maemo --> MeeGo should have been a minor bump in the road.
Someone who was there should write a "The Soul of a New Machine" book about it, so the rest of us can understand what happened.
Posted Jun 4, 2011 12:09 UTC (Sat) by n8willis (editor, #43041)
Definitely rewriting the toolkit stack is what kept Nokia from releasing a second Maemo phone, but your timing of events is mixed up. That started with the Harmattan cycle, in 2009, and well before MeeGo. For whatever reason, after the Trolltech purchase, someone decided that they had to dogfood Qt and Qt alone in all of their products, immediately, regardless of the costs.
The Deb-to-RPM transition came after the Maemo/Moblin->MeeGo merger, and isn't really related. Little more than a LSB-compliance move. So while Harmattan->MeeGo might could have been "a bump in the road" as you put it, Fremantle->Harmattan before it is what actually kept Nokia from expanding its offerings.
MeeGo is not simply "Maemo 6" or even "Maemo 7." In spite of Nokia's product-release problems, MeeGo has some significantly orthogonal goals, such as cross-UX-compatibility, and that's the really significant part. It may even be healthier for MeeGo that Nokia isn't pursuing it as hard, since that "Qt-only" emphasis (which was strategic- but not engineering-based) could prove to be thorny again (see Moblin's Clutter layer, for example).
Posted Jun 7, 2011 0:20 UTC (Tue) by felipec (guest, #75494)
Right now I don't think I can say much, just that IMO the issues were not technical.
Posted Jun 22, 2011 10:29 UTC (Wed) by job (guest, #670)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds