3 ms·
> Of course creating first Maemo on top of GTK and after that switching to QT sounded weird and with Meego there was other parties like Samsung and Intel meddli
by zokier 11y ago
> Of course creating first Maemo on top of GTK and after that switching to QT sounded weird and with Meego there was other parties like Samsung and Intel meddling around so they lost lot of steam in that transition too.
From my perspective one of the problems was that there wasn't just one major transition, but instead there were two. First was the GTK->Qt transition, and then just as that was stabilizing came new transition from Maemo to Meego which never really succeeded. I think the reason for the latters failure was that while there was a lot of reasons to be exited about Qt (over GTK), there was very little to be exited in Meego (over Maemo).
- trm42 11y agoFrom the end-user perspective both Maemo and Meego phones felt really good but the Meego seemed to have a bit more innovative and more fluid UX. Liked both of them and would've gladly bought them if there would've been any promise of continuity.
- digi_owl 11y agoThe whole Meego thing was a mess. Maemo had from the early days been Debian based. Then came Intel's Moblin in an attempt at pushing Atom for mobile devices (reason being that Intel had opted to forgo PCI on that variant to save power, and Microsoft balked at doing Windows on a x86 chip without PCI). Mobilin 1.0 was also Debian based. So at that point it seemed sensible for Nokia and Intel to combine their efforts and create Meego. But just as the jointed project was unveiled, Intel finalized Moblin 2.0. And it was RPM based. And Intel was heavily pushing for Meego to be that as well. Never mind that the N9 was really a last gen Maemo with some additions to make it Meego compatible.