Alternative Operating Systems Details
The development was silently resumed during the summer of 2011 by a handful of MeeGo developers (some of them previously active in the Mer project), after Nokia changed their strategy in February 2011. These developers were not satisfied with the way MeeGo had been governed behind closed doors especially after Nokia departed, and they were also concerned that MeeGo heavily depended on big companies which could stop supporting it, as was the case when Nokia abandoned MeeGo as part of their new strategy.
This was once again proven to be a problem after Intel, Samsung and the Linux Foundation announced they are going to create a new operating system called Tizen which will abandon most of the MeeGo legacy and especially application development APIs, focusing on HTML5 and using EFL instead of Qt for native applications.
Revival
After the Tizen project was announced, the revival of the Mer project was announced on the MeeGo mailing list,[2] with the promise that it will be developed and governed completely in the open as a meritocracy, unlike MeeGo and Tizen. Also, it will be based on the MeeGo code base and tools, aiming to provide just the equivalent of the MeeGo core with no default UI. The APIs for 3rd party application development are included, meaning that Qt, EFL and HTML5 would be all supported on the platform, and maybe even others if widely requested.
The project quickly started to gain traction among many open source developers who were previously involved in MeeGo, and it started being used by former MeeGo projects, such as the former MeeGo reference handset UX, now rebased on top of Mer and called Nemo Mobile, and a couple of projects targeting tablet UXes such as Cordia (a reimplementation of the Maemo 5 Hildon UX) and Plasma Active emerged on top of Mer. Equivalent Mer-based project of the former MeeGo IVI and Smart TV UXes are not yet known to exist.
One aim of the Mer community is to create, in a solid way, what previously was unable to be done with MeeGo; Mer is to become what MeeGo was expected to be but has not become. Also the Mer in future can become the MeeGo 2.0 when the Linux Foundation will assume it comply all MeeGo requirements as needed.
The development was silently resumed during the summer of 2011 by a handful of MeeGo developers (some of them previously active in the Mer project), after Nokia changed their strategy in February 2011. These developers were not satisfied with the way MeeGo had been governed behind closed doors especially after Nokia departed, and they were also concerned that MeeGo heavily depended on big companies which could stop supporting it, as was the case when Nokia abandoned MeeGo as part of their new strategy.
This was once again proven to be a problem after Intel, Samsung and the Linux Foundation announced they are going to create a new operating system called Tizen which will abandon most of the MeeGo legacy and especially application development APIs, focusing on HTML5 and using EFL instead of Qt for native applications.
Revival
After the Tizen project was announced, the revival of the Mer project was announced on the MeeGo mailing list,[2] with the promise that it will be developed and governed completely in the open as a meritocracy, unlike MeeGo and Tizen. Also, it will be based on the MeeGo code base and tools, aiming to provide just the equivalent of the MeeGo core with no default UI. The APIs for 3rd party application development are included, meaning that Qt, EFL and HTML5 would be all supported on the platform, and maybe even others if widely requested.
The project quickly started to gain traction among many open source developers who were previously involved in MeeGo, and it started being used by former MeeGo projects, such as the former MeeGo reference handset UX, now rebased on top of Mer and called Nemo Mobile, and a couple of projects targeting tablet UXes such as Cordia (a reimplementation of the Maemo 5 Hildon UX) and Plasma Active emerged on top of Mer. Equivalent Mer-based project of the former MeeGo IVI and Smart TV UXes are not yet known to exist.
One aim of the Mer community is to create, in a solid way, what previously was unable to be done with MeeGo; Mer is to become what MeeGo was expected to be but has not become. Also the Mer in future can become the MeeGo 2.0 when the Linux Foundation will assume it comply all MeeGo requirements as needed.
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
Alternative Operating Systems
No comments:
Post a Comment