feat(web/website): init
This adds a new Website/Docs for Snix, using Thulite / Doks, which is mostly hugo and a bit of npm. Change-Id: Iea10d4068fa783ec0ddd6bcaba5c8d92b1a1168f
This commit is contained in:
parent
2705517e6d
commit
91d8b86b39
55 changed files with 6205 additions and 0 deletions
26
web/content/docs/components/architecture.md
Normal file
26
web/content/docs/components/architecture.md
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
---
|
||||
title: "Architecture"
|
||||
slug: architecture
|
||||
description: ""
|
||||
summary: ""
|
||||
date: 2025-03-14T14:14:35+01:00
|
||||
lastmod: 2025-03-14T14:14:35+01:00
|
||||
draft: false
|
||||
weight: 31
|
||||
toc: true
|
||||
---
|
||||
|
||||
Snix is more decoupled than the existing, monolithic Nix implementation.
|
||||
|
||||
In practice, we expect to gain several benefits from this, such as:
|
||||
|
||||
* Ability to use different builders
|
||||
* Ability to use different store implementations
|
||||
* No monopolisation of the implementation, allowing users to replace components
|
||||
that they are unhappy with (up to and including the language evaluator)
|
||||
* Less hidden intra-dependencies between tools due to explicit RPC/IPC
|
||||
boundaries
|
||||
|
||||
In addition to many individual backend implementations, Builders and Store
|
||||
backends also provide a gRPC server and clients, allowing to plug in your own
|
||||
implementation.
|
||||
Loading…
Add table
Add a link
Reference in a new issue