Chloride

Chloride is an experimental bytecode streaming architecture. It avoids the bloat of the modern web by directly serving program bytecode to your client or browser. It achieves this by streaming sandboxed Wasm bytecode directly over custom sockets to native canvases and clients.

• Scripting-First: A critique of the modern web is its document-first approach, with things like heavy javascripts frameworks and flash being used to supplement interactivity. Interactivity is expected with this protocol.
• Zero-DOM Overhead: Client runtimes don't do HTML parsing, JavaScript glue code and otherwise avoid the complexities of the modern web. THey render their visuals directly to client pixel buffers or native canvases.
• Strict Isolation: Clients (such as conventional web browsers) contain programs inside a canvas, sandboxing them heavily. Wasm bytecode is also heavily sandboxed, only running within its standalone runtime or browser's Wasm engine.
• Minimal Footprint: An incredibly light micro-framed 8-byte socket header layout. Client memory consumption should be relatively low (especially compared to modern web apps.) It generally avoids a lot of the fluff of the modern web.

A small guide for new Chloride users and people seeking to host Chloride servers:

• How to Use Chloride

The complete draft specification is available as a PDF document:

• chloride_spec.pdf (Draft v1.0, PDF Specification)

URI Scheme: chloride://<host>[:<port>]/<path-to-module>

Port: 49130 (Complying with IANA experimental range 49128–49150)

Development discussion and IRC channels:

• IRC: #chloride on irc.chlorine.me
• Creator's Personal Site: chlorine.me