Just started my new blog to report (besides my OpenStreetMap activities) about my development activities for maemo, and in the meanwhile maemo changed to something else (or just changed its name). Was it a mistake to start a blog ;-)?

In my opinion, the strategy to merge is in principle right, but the timing could be better, and from the development and user view it creates new uncertainties where stability and evolutionary changes are necessary in the short time. It seems that Nokia possibly did not feel well enough with fremantle and harmattan road map and thought a strong partner would be better.

Practically there is some risk to annoy a huge number of people. It is necessary that both partners clarify their vision, get the technical merging through, define what is in and what is out quickly. Getting old and new developers into MeeGo still requires a mid-term convincing plan that make people invest in the platform while there is already money to earn somewhere else. Changing release policy by officially make the N900 supported for MeeGo would surely help, too, to reassure people quickly.

What does it mean for my applications? Since I’m building my own GUI framework and already was aware of the platform switch to Qt, nothing changes for me. In contrary, the fact that Gtk is in again, avoids me having to use Qt theming code for proper platform theming. Switching to RPM seems to be more politically motivated than technically (both parties have to balance out give and take), but since I have build RPMs in the past this should not real problem.Besides WifiInfo and the code for the virtual keyboard there are not that much platform specific APIs involved. I hope that are parts that are in.

Having access to a wider range of devices in future is in my direct interest, since one of the goals of Illumination (the underlying GUI library) is to get platform independent applications with exactly these varying functionalities and constraints. Thanks 😉

May you live in interesting times…