http://nokiaplanb.com/

So, what went wrong? In Meego's development.

Well nothing really... Intel is still trucking with it. Nokia is pulling out of it soon, for the most part.

If you were referring to Nokia's contribution to Meego, well than that's different.

Nokia falled to execute on that one. Plain and simple.

But curently Microsoft is the big bad make believe demon in the room.

2d

It is also possible to have VM to use moving GC which can optimize alive object to fit better to CPU cache and decrease cache misses. In OOP type of programs this can be a huge advantage which will make for example Java (or even Python) faster than C++. C++, even if it uses only references (no pointers, no pointers calculations, no arrays) are not able to use this method, because once references are de-referred and changed to pointers, one cannot move any alive object's place in the heap memory.

Also the moving GC allows to use heap memory de-fragmentation when there is long running OOP-program. At least my firefox (C++) will get increase of amount of cache misses about few days of heavy work, and I think it is caused by heap memory fragmentation (I plan to study this scientifically later.)

What this all means, is that Meego needs Dalvik VM (for example Alien Dalvik or FOSS one.) That way also Meego will immediately get ahead start of Android-"ecosystem's" number of applications nullified.

A very interesting read:

http://www.cringely.com/2011/02/burn...hips-at-nokia/

In fact, today Elop said in an Engadget interview (about MeeGo being it's plan B in case WP7 doesn't take off) that their plan B is to make sure "plan A doesn't fail".

I don't know about you guys, but there should be always be a second option. Having MeeGo as a skunkworks should be it.

Of course, making Qt compatible with WP7 and/or integrate Mono in MeeGo would have helped a lot too...

The thing about intel's involvement is that it doesn't necessarily focus on a specific kind of device. They want meego in kiosks, vehicles, tablets, nettops, IPTV boxes, etc...

Really they need a phone-maker that is going to heavily invest in the phone-specific user experience.

Come on, Maemo has a few badly optimised apps, unluckily they are the ones used most on a phone, apart from those, it's quite fast.
There's absolutely no reason Maemo couldn't be 10x-30x faster than now, if devs would just bother pointing out culprits and optimising them.

Android on the other hand, is hampered by it's VM.
Wishful thinking or (insert new coding paradigm buzzword) isn't going to change that.
Even on an intel atom 1.6GHz it runs like Maemo on a really bad day.
Allowing ring0 access for userland programs is a REALLY bad idea, it just goes to show how misguided the Android project is, no wonder they get their *** handed to them when they try to send patches to Linux. But to each their own.

Some good news:
Nokia entering the free software phone business was scaring off potential competition.
Now there is a market again for the many small start-ups that are developing Linux phones.
This might turn into something good in the end

I don't believe any of this. It just doesn't make any sense. They bought Qt in 2008 and has spent over two years to integrate it in Symbian. Why then dump it a few months before it'll be released?

And c'mon, why chose Elop as new CEO instead of Vanjoki? Sure there's been something going on. You can cover it up for a while but eventually the truth will come out, hopefully.

They should've asked why the chose an OS with no multitasking or dualcore support instead! WP7 is an epic fail and Nokia will be in deep trouble if they continue with Elop at the top.

Before elopocalypse N8 sold EXTREMELY good. Now I don't know though. And that is with the old ugly UI. If the new Qt based UI is super awesome Symbian phones would sky rocket in sales. If it sucks then yes going with something else on low end would've made more sense. But not now when the new UI is so close.