Well, I'd say the opposite happened: Nokia kept the profitable businesses (IP, network equiment, navigation) and transferred everything not worth keeping to Microsoft. And even got money in return. Pretty smart move.
So was Symbian for a long time. Granted, the language around ramping down Symbian was much more drastic (but only for an internal audience), but there was no move to stop making Symbian phones outright.
When something cut off at the knees by the CEO is outselling his pet project five to one you know that the CEO is not working for the company that he's supposed to be running.
Which is very close to what Apple did with the iPad and Mac. Sometimes you have to be able to move past a dead end by drastic measures.
PS: Symbian (or to be precise, S60) was crap. Crap to use, crap to develop, and crap to develop for (I did all three). Good riddance.
... of which none did deliver or were stillborn. The cross platformness of Qt was compromised from the start with two competing UI frameworks libdui for Harmattan and Orbit for Symbian. This is a good article about that mess. And from what we know about Meltemi, it would have been a third, incompatible framework.
Nokia did achieve only the minimum target for Symbian, and that is to retrofit Qt 4.8 to Symbian 9.2/^3.
Before anybody blames Elop for this, 90% of it happened before his time.
Like Apple, currently shopping around for another chip manufacturer after Samsung raised prices, (to earn back billion dollar fine which will most likely be overturned on appeal).
I'm glad to see your comment already at +5 - it's spot on, couldn't have written it better. Qualcomm is the achilles heel for Nokia, and making a change to any other chipset vendor will be really hard. The ramp down of Nokia's production of own chipsets produced by TI is by the way another severely limiting factor for Nokia to continue to deliver any Symbian based devices (not that there would be a big market for them now).
Nokia's failed chipset strategy during the last five years is monumental, and deadly when combined with the Qualcomm lawsuit outcome.
maybe having a resume that has software jobs continuously from the 80's thru the present is considered a give-away of your age and its immediately circular-binned by HR and most hiring mgrs?
Possibly... might be better to just list the last ten years.
This was a company internal presentation, not for journalists. If you watch the whole video, it becomes clear that this was not a controlled leak, there are other references to ongoing work which I seriously doubt Elop wants to have out in public.
Intel hired a lot of the Nokia people working on Maemo and Meego. I'm very curious what they can pull off, and I wish them good luck! Elop's concerns were not the technology though, but the execution. Shooting him as the messenger makes no sense.
You're paranoid. Plus the poison pill agreement is not relevant anymore now that Qt is under the LGPL (it was drafted before the license change). Check the work on open governance for Qt.
To learn from the former Trolls how to create great software. The framework is important, but so are the people working on it, and how they get things done.
All phones based on SymbianOS 9.1 and later require signing, and that includes all Nokia phones with S60 release 3. Your N70 is using S60 release 2, which didn't require signing.
Dr Tannenbaum may well be correct that from theoretical considerations a microkernel is superior. But AFAIK after 15+ years of maintaining that, he and his supporters still do not have a useful exemplar
RTFA:
Are Microkernels for Real?
In a word: yes. There were endless comments on Slashdot Monday (May 8) of the form: "If microkernels are so good, why aren't there any?" Actually there are. Besides MINIX 3, there are:
QNX
Integrity
PikeOS
Symbian
L4Linux
Singularity
K42
Mac OS X
HURD
Coyotos
I'd consider QNX for example quite useful to help nuclear power plants from blowing up. And Symbian, while not a true microkernel, has shipped in probably well over one hundred millions phones.
Slashdot Mirror
Well, I'd say the opposite happened: Nokia kept the profitable businesses (IP, network equiment, navigation) and transferred everything not worth keeping to Microsoft. And even got money in return. Pretty smart move.
So was Symbian for a long time. Granted, the language around ramping down Symbian was much more drastic (but only for an internal audience), but there was no move to stop making Symbian phones outright.
A classic case of innovator's dilemma I'm afraid.
When something cut off at the knees by the CEO is outselling his pet project five to one you know that the CEO is not working for the company that he's supposed to be running.
Which is very close to what Apple did with the iPad and Mac. Sometimes you have to be able to move past a dead end by drastic measures.
PS: Symbian (or to be precise, S60) was crap. Crap to use, crap to develop, and crap to develop for (I did all three). Good riddance.
However, in 2009 and in 2010, Nokia was growing its sales...
Not true for the smartphone segment (which is what the burning platform memo addresses):
http://en.wikipedia.org/wiki/File:World_Wide_Smartphone_Sales_Share.png (based on Garner data, similar graphs which go back far enough are easily found)
The decline started already in 2007, and Android started surpassing Symbian during 2010. The burning platform memo was from early 2011.
Psion Organizer: 1984
Mobile development started well before Apple and Android.
... of which none did deliver or were stillborn. The cross platformness of Qt was compromised from the start with two competing UI frameworks libdui for Harmattan and Orbit for Symbian. This is a good article about that mess. And from what we know about Meltemi, it would have been a third, incompatible framework.
Nokia did achieve only the minimum target for Symbian, and that is to retrofit Qt 4.8 to Symbian 9.2/^3.
Before anybody blames Elop for this, 90% of it happened before his time.
Like Apple, currently shopping around for another chip manufacturer after Samsung raised prices, (to earn back billion dollar fine which will most likely be overturned on appeal).
Nice story, but not true.
I'm glad to see your comment already at +5 - it's spot on, couldn't have written it better. Qualcomm is the achilles heel for Nokia, and making a change to any other chipset vendor will be really hard. The ramp down of Nokia's production of own chipsets produced by TI is by the way another severely limiting factor for Nokia to continue to deliver any Symbian based devices (not that there would be a big market for them now).
Nokia's failed chipset strategy during the last five years is monumental, and deadly when combined with the Qualcomm lawsuit outcome.
For instance, it was used in Maemo - but then replaced with something GTK-based.
You got that the wrong way around. Maemo used GTK until the Fremantle release, but switched to Qt for Harmattan.
... or Fiasko.
They had the ... dominant dumbphone OS.
Uhm, they still have S40 and are still selling quite a bunch of S40 based phones (especially the Asha series).
Nope, you couldn't target S40 with Qt.
maybe having a resume that has software jobs continuously from the 80's thru the present is considered a give-away of your age and its immediately circular-binned by HR and most hiring mgrs?
Possibly... might be better to just list the last ten years.
It was called N950, and was killed into "developers only" after Elop came.
No, it was killed before he came, around Summer 2010.
Right: NewtonOS 2.0, ca. 1995:
http://manuals.info.apple.com/Apple_Support_Area/Manuals/newton/NewtonProgrammerRef20.PDF
Chapters 18 and 19, routing and transports.
This was a company internal presentation, not for journalists. If you watch the whole video, it becomes clear that this was not a controlled leak, there are other references to ongoing work which I seriously doubt Elop wants to have out in public.
Intel hired a lot of the Nokia people working on Maemo and Meego. I'm very curious what they can pull off, and I wish them good luck! Elop's concerns were not the technology though, but the execution. Shooting him as the messenger makes no sense.
You're paranoid. Plus the poison pill agreement is not relevant anymore now that Qt is under the LGPL (it was drafted before the license change). Check the work on open governance for Qt.
To learn from the former Trolls how to create great software. The framework is important, but so are the people working on it, and how they get things done.
My workplace (over 100k users) just migrated to Microsoft hosted email. And we're in some areas direct competitors of Microsoft.
...this is going to draw in QT Embedded
What makes you think this?
Care to shed some more light on this too?
All phones based on SymbianOS 9.1 and later require signing, and that includes all Nokia phones with S60 release 3. Your N70 is using S60 release 2, which didn't require signing.
RTFA:
I'd consider QNX for example quite useful to help nuclear power plants from blowing up. And Symbian, while not a true microkernel, has shipped in probably well over one hundred millions phones.
However, they lock out Linux users... as well as anybody not living in the US.
Remember that players have individual keys. If a hardware player is revoked, it is only one specific physical player which is affected.
Wrong.