![]() ![]() ![]() The MeeGo project has also promised some tools and/or services whereby apps can be validated for compliance. This is essentially a list of standard software parts that developers can draw from when writing and porting their apps to the initial MeeGo release. Just as “standardized parts” reduce maintenance and support costs in practically every machine since Ely Whitney’s cotton gin, standardized native environments exist to tame the unruly bazaar, foster re-use and create engineering efficiency.Įventually, the MeeGo project will announce its first “final” API, or application programming interface. So, projects like Maemo, Moblin, and now MeeGo aim to bring coherence by “standardizing” things like what libraries are present, and what versions of tools are used to build binaries. Ironically, one drawback to native environments is that “full” Linux is just incredibly vast. Software, Software Everywhere, and Not a Bit to Twiddle Palm’s Netkit-based WebOS has certainly shown that Javascript/DOM/XML/CSS are increasingly able to provide a viable alternative to traditional managed environments, on phones and elsewhere. However, it will also support “web runtime” apps. Like Maemo and Moblin, MeeGo will support native apps. Calls to the underlying OS and hardware can be limited by or filtered for this runtime, affording some global control over app behavior. In a managed environment, developers primarily write/port apps to run atop a runtime, such as a virtual machine. Porting existing open source apps is comparatively easy. Developers link in standard GNU/Linux libraries, and use standard Linux calls, because they are writing native Linux apps. Native Linux environments like Maemo and Moblin are beloved for their familiarity, flexibility, and performance. Both approaches are good they are just different. NET, Android, and the various Linux/Java mobile phone stacks. This contrasts with managed environments like. However, from materials published so far, it’s pretty easy to guess how the project aims to exploit Maemo and Moblin similarities, where it plans to chart a course of its own (mainly to encourage portability, it seems), and where it could have some work to do ironing out differences between the stacks.īoth Maemo and Moblin emphasize native Linux development. Furthermore, given that the Linux kernel supports more than two-dozen architectures, can’t open source app stacks evolve beyond architectural boundaries? Sure they can, and many have.ĭetails about MeeGo are still emerging. Put aside that difference, though, and the projects are peas in a pod. Maemo targets ARM, while Moblin aims to enable devices with Intel Architecture (commonly “x86”) processors. Some may be surprised by the merger, announced this week, of the open source Maemo and Moblin projects, given their architectural differences. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |