multiplexer

The problem is, without generics you need to create a new multiplexer for every type of channel payload.

What I find most amazing is how the kernel is more like a file system multiplexer.

That kept the network happy, and was enough for our multiplexer to then internally route to the correct backend.

Editors are replicating terminal multiplexer functionalities - tabs, windows, and now with terminal emulation they have become terminal multiplexers.

The kernel is effectively an I/O and network multiplexer for synthetic file systems that abstracts common resources to enable location/network transparency, single system imaging and interface uniformity.

It uses a proper IRC client running on a server (WeeChat in a terminal multiplexer) and connects to that via WebSockets.

Easy on paper: model tells you what to trade, and you already have a multiplexer.

In a sense, your system does have one large multiplexer to access all of memory.

However, such integration requires the editor to have specific knowledge of the terminal multiplexer, e.g.

The world can benefit from something that is built as both an editor and a terminal multiplexer from the very beginning.

> What I find most amazing is how the kernel is more like a file system multiplexer.

A multiplexer like this can work around such (assumed) well-intentioned but poorly implemented protections.

The device is "just" a computer-designed multiplexer.

Having the editor and the terminal multiplexer communicating with each other is basically a modular approach to the "editor and terminal multiplexer in one" idea, which allows you to combine the editor and the terminal multiplexer freely.

I am not completely sure what an "http multiplexer" actually is.