Fuchsia OS: A New OS By Google.

Fuchisa OS

This week, Chrome OS received a major update, bringing a new ‘Better Together’ collection of settings that make your Chromebook better when used with an Android phone. Chrome OS 71 also includes some updates to the relatively new Linux app support, including the ability to manually shut down the Linux virtual machine without having to restart your device.

Other changes include autocomplete in Launcher search and semi-full pages in the Launcher that don’t require the entire app grid to be filled before creating a new screen. There is also an “adaptive top UI in Chrome browser based on user scrolling,” while Family Link’s new screen time limits and Android app management features are tied to this update.

In an interesting twist for both Android and Fuchsia, Google’s in-development OS is getting both its app development SDK and a “device” added to the Android Open Source Project. The purposes for these are still unclear, but we’ve made the Fuchsia SDK available for developers to browse.

It’s impossible to say for sure at this stage, but it seems highly likely to me that Fuchsia app development will be accessible directly from Android Studio, thanks to its inclusion in AOSP. And at the rate that these changes have been coming from Google, we may very well see Fuchsia be legitimized in the coming months.

Chinese multinational Huawei appears to be the first OEM trialling Google’s fledgling Fuchsia OS (operating system) on one of its platforms.

The company is working on making the potential Android replacement run on its Kirin 970 processor-powered Honor Play smartphone.

Google already has two operating systems: Android (for mobile) and Chrome (netbooks, etc.) which is essentially just Linux running web apps, with no native development.

The Fuerechsia OS, by contrast, is based on a very small custom kernel from Google called Zircon which unusually, comes with some elements written in C++.

It appears be being developed by Google as a unified platform for mobile and heavier-weight devices, potentially with applications in embedded systems too.

Zircon device drivers run in what’s called ‘user land’, meaning they’re not given fully elevated privileges and can be isolated better. In user land, everything that a driver does has to go via the kernel first before hitting the actual computer’s resources


Sharing this helps a lot

Leave a Reply

Your email address will not be published. Required fields are marked *