Ecosystem

min2max. Maximum functionality, minimum resources.

A collection of ultralight web tools. Each one solves one problem, ships with zero dependencies, and respects every byte it occupies.

Products

minline.js

1337 B brotli JavaScript

DOM-based templating and i18n. 15 filters, CSV translations, user preferences. No virtual DOM, no build step. Works with your existing HTML.

minline.run →

minline.css

4 kB CSS

Semantic CSS framework. OKLCH colours, automatic dark and light theme via light-dark(). Forms, buttons, dialogs, complete design system. No build step, no configuration.

minline.run →

htm/a

6.7 kB gzipped Rust, JavaScript

Fully server-side reactivity framework. EASL pattern: Event, Action, State, Layout. 75x smaller than React, zero dependencies. Rust server, 4 KB JS client. Full UI without the framework tax.

htma.run →

GBLN

340 kB Rust, C, Go + 10 more

Goblin Bounded Lean Notation: type-safe, AI-optimised data format for minimal communication. 86% fewer tokens than JSON, smaller than TOML and TOON. Memory-bounded types, 13 language bindings, deterministic parsing.

gbln.org →

paqmin

3.8 kB Rust, Shell

Self-verifying signed TAR packages. Ed25519 signatures, SHA256 hashes, permission validation. No package registry, no configuration. One maintainer key.

Closed beta

Shellboard

2,400 kB Rust, Lua

Unix shell with real-time system visualisation. Split view: graphs and tables above, shell prompt below. Every UI interaction generates a visible command. Single Rust binary, Lua extensible. Teaches Unix by design.

Coming soon

CASTD

The engine behind this site.

Stackless web server. Rust binary, Lua extensions, SQLite storage, CAST template language. 2 MB. Zero dependencies. Serves this entire site, including server-side form handling, from a FreeBSD jail.

Every page you see here is proof of concept.

Performance

Accessibility

Best Practices

SEO

0.2s FCP

0.3s LCP

0 ms TBT

0.019 CLS

~122 KB Total

11 Requests

github.com/VivianVossNet/castd →

The Principle

Every tool in this ecosystem follows one rule: if it can be smaller without losing function, it must be. Not minimalism as aesthetic. Minimalism as engineering discipline.

KISS for developers and users alike. One function, one job. No side effects, no hidden complexity, no clever shortcuts that cost you later.

Never guess, always verify. Framework and content stay separated. Destructive operations require approval. When in doubt, stop and ask. Unix composability over monolithic convenience.

Occam's razor as method: trace every problem to its root cause, solve it cleanly with the smallest possible effort, and never reinvent what Unix-like tools already handle. Build with the philosophy in mind, not against it.