| |||||||||||||
Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica)Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica)Posted Sep 12, 2011 11:49 UTC (Mon) by boudewijn (subscriber, #14185)In reply to: Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica) by spaetz Parent article: Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica)
Number of phones: at least one... Which is about as many as there were Maemo phones. You might argue, if you insist, but then you're part of the problem, that harmattan is not MeeGo, but to an application developer it doesn't matter. The api's are the same. Packaging as deb instead of rpm is completely trivial. Anyone who has a problem with that is not a professional.
It was also not the switch to Qt on its own that took time. There were already excellent Qt-based applications for Fremantle that behaved indistinguishable from other apps on the platform.
But doing a new toolkit on top of Qt, then doing another and another, that took lots of time and was not a good idea. Especially when the result, MeegoTouch, turned out to be so bad. It's a pity we didn't have QML earlier.
(Log in to post comments)
Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica) Posted Sep 12, 2011 12:04 UTC (Mon) by juliank (subscriber, #45896) [Link]
> Packaging as deb instead of rpm is completely trivial.
Not if done correctly, they are entirely different (but mostly equivalent) file formats and conventions.
> It was also not the switch to Qt on its own that took time.
> It's a pity we didn't have QML earlier.
But I didn't take a closer look at it; I wrote my last graphical
Intel denies giving up on MeeGo, but that doesn't mean much (Ars technica) Posted Sep 12, 2011 12:14 UTC (Mon) by spaetz (subscriber, #32870) [Link]
I don't want to spam LWN with more replies. If you want to persue this any further, contact me at Sebastian@SSpaeth.de and I'll continue the discussion.
|
|||||||||||||