Why is Google doing Fuchsia

Fuchsia OS - Google's future operating system?

Google Fuchsia is based on a modular design that breaks with the concept of the app. Software units are called Packages (Packages). At a package it is a selection of files - including Metadata, manifest files, and executables. The latter are in Google terminology Components (Components) called.

Fuchsia components come closest to what we call apps today. Each component fulfills a specific task and can be combined with other components to enable complex applications. The parts of a component include a manifest file and the associated code. Components always run in their own sandbox, access objects via namespaces and publish them via an export directory. At Fuchsia OS there are two main types of components: Models (Modules) and Agents (Agents).

Components in the role of a Agents work in the background and provide services for other components. An agent is called either by another component or by the system - for example in response to certain triggers such as push notifications or other processes on the screen.

At Modules These are components with a user interface that are executed in the foreground so that they are visible to the user. Each module within the operating system was developed for a specific task and is marked accordingly so that it can be called up automatically as soon as it is needed. This is done using the function of the module, which is based on what Verbs (Verbs) and Nouns (Noun) can be described.

Each module includes a list of Verbsindicating what work the module can do and a list of nounthat represent entities that are being worked with. The term Entity According to Google terminology, includes all clearly identifiable people, places, things, events or concepts that are available as structured data objects that can be referenced and that can be accessed, presented, manipulated or released.

In thepractice Working with the real-time operating system Fuchsia is as follows: As soon as a user performs an action, Fuchsia OS automatically determines the appropriate module for the task. The desired action is translated into a combination of verb and noun. The system then calls up a list of all modules that support the desired verb and, in the next step, filters for the module that can also handle the desired noun.

Related modules can be broken down into so-called Stories group. Stories combine various actions and tasks according to current requirements and are intended to enable users to put together complex applications according to their own ideas and requirements.