Propagating a novel operating system (OS) can often be a frustrating chicken-vs-egg scenario, as many abandoned platforms and even current ones like Linux can demonstrate. An OS won’t gain many converts without a reasonable stream of ready-made applications as well as the necessary ecosystem support (especially device drivers). In open source contexts, this is compounded by Digital Rights Management (DRM) and similar sticky, usually legal, bogeys.
Maintaining a compelling closed ecosystem, such as Apple has chosen with its various OS offerings, certainly goes a long way toward solving those hurdles. On the other hand, Google’s breadth of services, brand recognition and sheer size have quickly carved out secure toeholds for the more open Android and undoubtedly Chrome OS. And there are already several well-established (although shrinking) platforms occupying the rest of the market slots… so where’s the space for upstart MeeGo?
The recent article here rhetorically asked Why MeeGo and that’s not the point today. Rather, I want to cover what’s going on in porting and packaging, and what that might mean for MeeGo’s possibilities. Continue reading