ned
What it does
Section titled “What it does”ned’s core tenet is everything is a stream. Built on nix-effects (using effect rotation, scoped handlers, and function parameters as effects for dependency injection), ned’s primitives are effectful streams. Concerns that a configuration framework usually hard-codes (topology transitions, class forwards, deduplication) become ordinary stream composition and transformation.
Core concepts
Section titled “Core concepts”- Stream (
ST a), a lazy, pull based effectful sequence of items, with a fluent API for composition. By convention auser-sname means “a user stream” - Driver (
request-s -> response-s), a stream transformation responsible for performing side effects, named after Cycle.js drivers
Key features
Section titled “Key features”- Minimal, complete kernel, feature-minimal by design; the kernel is already complete
- Not NixOS-specific, usable for anything you use Nix for, not just configurations
- 0ver, zero-based versioning (0ver)
Role in the ecosystem
Section titled “Role in the ecosystem”ned is the reactive substrate of the ecosystem. den uses it as its stream-based core, dnzl builds an actor system on its stream-cycles, and zen uses ned cycles for the module fixpoint.
Source Code Support this project