openv

Features

• Easy to install and run on various platforms (primarily Linux and the web)
• Modular architecture allows developers to roll their own API for anything you could think of
• Architecture designed around a central observable state (the "registry") with developer-designed APIs
• Broadcast the operating system over a generic transport layer (e.g. WebSocket, postMessage, etc.)
• Open source and community-driven development

Architecture

openv is built around a central observable state called the "registry". This registry holds all the data and state of the operating environment, and can be observed and modified by APIs. Something that makes openv unique compared to other operating systems is that the all APIs are selected by the developer.

While there is a core set of APIs that are published and maintained by the openv project, they are not required to run openv. For example, if the developer is running a restricted environment that doesn't need the entirety of party.openv.fs, they can choose an alternate implementation (or none at all).

Alternate implementations of APIs can be created by anyone, and the official openv APIs are simply guidelines for compatibility. Developers are free to design the implementations of the APIs however they see fit, though they should replicate the default interface if the implementation will be published as an override in some distribution of openv. (e.g. distribute as com.example.fs instead of party.openv.fs if the implementation is not compatible with the default).