Linked by Thom Holwerda on Sat 22nd Oct 2011 22:24 UTC
PDAs, Cellphones, Wireless Remember back when Nokia jumped to Windows Phone 7, abandoning all other platforms and future directions? Remember Elop's infamous 'burning platform' memo was coveniently 'leaked' to the web? Remember how Elop claimed Windows Phone 7 was the only way forward, since nothing else inside the company would be ready for prime time soon enough? Remember how I thought this was a very good and sane decision? Well, the first reviews of what will be the only MeeGo handset from Nokia (the N9) are in, and well... To whoever decided to go WP7 and ditch MeeGo: I don't like you. To myself: I'm an idiot for arguing this was a good idea.
Thread beginning with comment 493965
To view parent comment, click here.
To read all comments associated with this story, please click here.
henderson101
Member since:
2006-05-30

Except, that would be selling the platform short by a country mile.

Also, providing a VM isn't a magic sticking plaster. What would be the reason to buy an N9 over a Galaxy 2S? There's nothing really compelling and the user interface is really something that might be recreated if it comes down to it. My N810 is now sporting a N900 style Maemo5 task display and app launcher. It's pretty well implemented and there's no reason that the Meego UI can't be aped on another platform if it comes to that.

Reply Parent Score: 2

lemur2 Member since:
2007-02-17

Except, that would be selling the platform short by a country mile.


If a device such as the N9 included Alien Dalvik, then it would inherit all of the Android ecosystem AS WELL as being able to run native Meego/Qt apps. This would be a capability beyond that of any Android/iOS/WP7 device on its own.

How is that observation selling the platform short?

Reply Parent Score: 1

henderson101 Member since:
2006-05-30

"Except, that would be selling the platform short by a country mile.


If a device such as the N9 included Alien Dalvik, then it would inherit all of the Android ecosystem AS WELL as being able to run native Meego/Qt apps.
"

And where are these "Meego" apps going to spring from? Where is my incentive, as a user, to invest in a platform with a schizophrenic eco system? Why do I use Meego apps that are half baked, when I can have mature Android apps? It's not really that hard to make a compelling argument against this. This is the ultimate question that puts many emerging platforms on a knife edge - they have to ask themselves (and their users) should we spend a lot of time building a better native platform, or is providing a set of runtimes to allow other platform exes to run going to be a better way? The former builds character, the latter is a quick fix which may ultimately backfire.

This would be a capability beyond that of any Android/iOS/WP7 device on its own.


But what real benefit would it have? Why is using an Android app to bootstrap a platform a better plan, rather than developing a real native app? This is the issue Haiku and Syllable both faced. Haiku now has a port of Qt, AFAIK Syllable still sticks to the premise "native is best". Haiku appears to be progressing faster (but then it was always a more mature platform to begin with, being that it reimplemented a stable commercially delivered OS), but where is the incentive to use the native API when I can write apps using Qt? If you don't understand that quandary, you don't really have anything useful to say.

How is that observation selling the platform short?


Because, a platform is surely worth more than a lazy sticking plaster fix approach to getting applications? You are looking at the acquisition of apps for the platform to run with a tunnel vision, I'm telling you that without dedicated support form a multitude of developers, it will stall the Meego app eco system.

Reply Parent Score: 2