One thing we can easily highlight about Google is that its projects sometimes seem to compete with each other, but it's not a strategic mistake—quite the opposite. When it comes to operating systems, Android's success is overwhelming and Chrome OS numbers keep rising, yet there's a background project that could replace them both. Its code name is Fuchsia, and although it technically has an open source profile, it's not based on Linux.
Android carries several problems, the most critical being the lack of a solid platform to deliver updates to users. Once patches reach the code, everything depends on OEMs and carriers, who show little interest in supporting devices beyond their essential commitments. These and other deficiencies have followed the operating system for years, which raises a very interesting question: What would Android be like if Google could develop it from scratch, in 2017, with all its current knowledge? The answer is Fuchsia.
Fuchsia at a glance
The first details about this mysterious operating system surfaced in August 2016 as a simple command line. Today, Fuchsia has a much more elaborate interface idea (dubbed Armadillo), with a dedicated tablet mode, split screens, and suggestion panels. For now it's little more than a skeleton, and the truly interesting part of the operating system lies in the low level.
In simple terms, Fuchsia discards the Linux kernel and the use of the GPL license, in favor of an internal microkernel called Magenta, and a combination of Apache 2.0, MIT, and BSD (3-Clause) licenses. Also left behind is all the legacy material tied to Java. The interface is built with the Flutter SDK, and apps are based on Dart.
Google I/O 2017 is a week away. Ideally, the company will share more details about Fuchsia there, but something tells me that won't be the case (I hope I'm wrong). Fuchsia has all the characteristics of a very long-term project, and that "distance" might be necessary to develop a stable transition from Android and Chrome OS to the new system.
