Chromium has deleted components from its repository that were necessary for the assembly of the Chrome browser for the Fuchsia operating system, according to a report. This indicates that Fuchsia support in Chrome was an experiment that is now discontinued. The termination of support is attributed to the development of Fuchsia for workstations. While support for the Webengine and Webrunner browser components for Fuchsia will continue, a full-fledged Chrome browser will no longer be provided. It seems that further development of Fuchsia will be focused on consumer devices such as home automation systems, smart photo frames, and speakers.
Fuchsia, which is based on the micro-kernel Zircon (derived from the project LK), is designed for various devices including smartphones and personal computers. Zircon expands on LK’s achievements by adding support for processes and divided libraries, a user-level security processing system based on capability. Drivers are implemented as dynamic libraries in Fuchsia, operating through the devhost process and controlled by the device manager (DEVMG, Device Manager).
Fuchsia has its own graphic interface written in the DART language using the Flutter framework. The project is also developing a framework for constructing user interfaces called Peridot, a package manager named Fargo, a standard library libc, a rendering system called Escher, a Vulkan driver called magma, a composite manager called scenic, and file systems such as Minfs, Memfs, Thinfs (FAT in GO), and Blobfs. Support is provided for C/C++, DART, and systemic components, and the use of Rust, Go, and Python is also allowed in certain system components.
During the loading process of Fuchsia, several components