Linked by Thom Holwerda on Thu 11th Oct 2012 21:41 UTC
PDAs, Cellphones, Wireless It's a long read - but totally and utterly worth it. After interviewing ten former and current Nokia employees, and combining their insider information with publicly available information, Sampsa Kurri has written a long and detailed article about the history of Maemo and MeeGo within Nokia, and everything that went wrong - which is a lot. It's sad tale, one that reads almost like a manual on how to not run a large company. Still, between the bad decisions and frustrations, there's a red thread of hope that leads to Jolla.
Permalink for comment 538674
To read all comments associated with this story, please click here.
RE[5]: Remember...
by Neolander on Tue 16th Oct 2012 14:13 UTC in reply to "RE[4]: Remember..."
Member since:

How many versions of Symbian are there?

Not bothering to support old hardware with new software releases is a common, although indeed despicable thing to do. I don't think it matters so much to the vast majority of end users in the end, judging by how little they cared about the very same thing happening to Android anytime the latest update bumped up hardware requirements.

Why does a version exist with touch?

It seems that there are enough people out there who like the feeling of fondling a greasy LCD for there to be a significant market for this. The question to ask in this case would probably be that of why it took them so long to release it and get it right.

Why did Nokia screw up Maemo so badly in the process, changing the API and ABI with every new release

I think the aim was to improve Moblin compatibility, but I may be wrong.

and why was the development environment tied to LINUX and fairly non trivial to install up till Diablo?

Apparently, Nokia has always have a hard time releasing quality development tools for their phones. I would bet that they made the mistake of not considering something that is important enough.

Why did Nokia lie about moving from GTK+ to Qt? I mean, really out and out lie? We were told "no, we will still support GTK+, you're efforts are not pointless", then it was dropped as the tool-kit.

Yet another standard and despicable business practice. I honestly can't figure out why it happens, but executives seem very kind of ignoring widely publicized product issues for a long time, either by not saying anything or claiming that it's users' fault for holding the failing product wrong.

The fact that the N9 exists at all is a testament to the fact that someone paired down the specs for once and tried to make a product without the entire LINUX kitchen sink included out of the box.

And since this is a very painful thing to do once your brain is stuck in the endless nefarious cycle of development hell, I was applauding the ones who did this.

Apple may well have squandered a large amount of cash and lost face on Copland, but dropping both Classic and Copland actually worked out for the best in the log run. More luck than judgement, but OSX is not bad.

Heh, we'll see how well that OS reboot option will work for Nokia with Windows Phone. But indeed, Apple did manage to get OS X right in the long run, though they also did take their time for that...

Edited 2012-10-16 14:21 UTC

Reply Parent Score: 1