flake-parts provides the options that represent standard flake attributes and establishes a way of working with system. Opinionated features are provided by an ecosystem of modules that you can import.
For me flake-parts is the best way to manage Nix flakes
28 votes, 29 comments. Raw flakes get messy fast with repeated forAllSystems boilerplate and nested attributes everywhere. flake-parts uses a module…
Speed up your Nix Flake builds & caching with Devour-Flake & Cachix
I put together a guide on how to make your Nix flake builds and caching a lot faster using devour-flake alongside Cachix, and I wanted to share it…
flo-bit/streamplace-overlay
Contribute to flo-bit/streamplace-overlay development by creating an account on GitHub.
Shoelace: A forward-thinking library of web components.
Hand-crafted custom elements for any occasion.
sugarcube
Design tokens, generated CSS, and optional components. Build front ends on strong, reusable foundations.
Differ - Adaptive Software
Build software that adapts to each user — without forks or feature flags. One codebase, infinite variants.
Differ - Adaptive Software
Build software that adapts to each user — without forks or feature flags. One codebase, infinite variants.
Category Theory for Programmers: The Preface
Table of Contents Part One Category: The Essence of Composition Types and Functions Categories Great and Small Kleisli Categories Products and Coproducts Simple Algebraic Data Types Functors Functo…
Docs as Code — No SilverBullet
No SilverBullet: notes on building SilverBullet and other things.
Architectural mismatch: why reuse is so hard
Why isn't there more progress toward building systems from existing parts? One answer is that the assumptions of the parts about their intended environment are implicit and either don't match the actual environment or conflict with those of other parts. The authors explore these problems in the context of their own experience with a compositional approach.<>
Coeffects: a calculus of context-dependent computation
The notion of context in functional languages no longer refers just to variables in scope. Context can capture additional properties of variables (usage patterns in linear logics; caching requirements in dataflow languages) as well as additional resources or properties of the execution environment (rebindable resources; platform version in a cross-platform application). The recently introduced notion of coeffects captures the latter, whole-context properties, but it failed to capture fine-grained per-variable properties.We remedy this by developing a generalized coeffect system with annotations indexed by a coeffect shape. By instantiating a concrete shape, our system captures previously studied flat (whole-context) coeffects, but also structural (per-variable) coeffects, making coeffect analyses more useful. We show that the structural system enjoys desirable syntactic properties and we give a categorical semantics using extended notions of indexed comonad.The examples presented in this paper are based on analysis of established language features (liveness, linear logics, dataflow, dynamic scoping) and we argue that such context-aware properties will also be useful for future development of languages for increasingly heterogeneous and distributed platforms.
bb
bb can control, customize, and automate itself, laying the groundwork for your own software factory.
