Recently Google has released the changes it has made for indicate the transition from your new operating system "Fuchsia OS" to the final internal test stage «dogfooding», which implies the use of the product in the daily activities of the employees, before taking it to ordinary users.
In this stage, the product is in a state that has already passed basic tests of special quality assessment teams. Before delivering the product to the general public, also a final check is done among your employees they are not involved in development.
About Fuchsia
For those who are still unaware of Google's Fuchsia project, you should know that the search giant is developing a universal operating system that can work on any type of device, from workstations and smartphones to embedded and consumer equipment. The development is based on the experience of creating the Android platform and takes into account deficiencies in the field of scale and safety.
The system is based on the Zircon microkernel, based on the achievements of the LK project, expanded for use on various classes of devices, including smartphones and personal computers.
Zircon extends LK with support for shared libraries and processes, a user level, an object processing system, and a capabilities-based security model.
Controllers are implemented as dynamic libraries that operate in user space, loaded by the devhost process and managed by the device manager (devmg, Device Manager).
The project has its own graphical interface written in a Dart language, plus the project also develops a framework for building Peridot user interfaces, Fargo package manager, libc standard library, Escher rendering system, Magma Vulkan driver, Scenic composite manager, MinFS, MemFS, ThinFS (Go language FAT file systems) and Blobfs file systems, as well Like the FVM Sections manager, application development provides support for the C / C ++ language, Dart, among other components.
During the boot process, a system administrator is used that includes appmgr to create the initial software environment, sysmgr to create the boot environment, and basemgr to configure the user environment and organize the login.
For compatibility with Linux in fuchsia proposed Machina library, which allows you to run Linux-program in a special isolated virtual machine formed by using a hypervisor based on the specifications of the zircon and Virtio kernel, by analogy with the organized way the launch Linux-applications on Chrome OS.
What changes are there in dogfooding?
In this final internal version, it is mentioned that the fuchsia.cobalt.SystemDataUpdater component was added to the Omaha update delivery management system, testing Chrome and Chrome OS editions and provides instructions for transferring devices to the new "dogfood-release" branch using the fx utility (similar to adb for Fuchsia).
Also bootloader sets have been added for the «dogfooding» branch to the continuous integration system and separate metrics are included in the Fuchsia platform to evaluate test results.
Comments on the changes to Fuchsia they mention two links to deliver the updates fuchsia-updates.googleusercontent.com and arm64.dogfood-release.astro.fuchsia.com, in the second link Astro is the codename of the Google Nest Hub smart display, which is apparently used by Google employees as a prototype to test Fuchsia instead of the standard Cast Platform firmware.
The Nest Hub interface is based on the Dragonglass app that uses the Flutter framework, which is also supported by Fuchsia.
Finally it is expected that if everything goes well at this stage of internal testing among employees, the final version for release to the public could come. Although it is clear that the reason for still keeping it in the testing phase is to polish all those details and errors that are detected.
But the real test will be in the launch to the public, in addition to that many wonder if it was not another Google product that if it does not meet their expectations will end up as another more abandoned product.
Source: https://9to5google.com
I knew about the existence of this project but had never read anything in particular about it. I liked the presentation. Now it's time to see if it is a valid replacement with apps or not.