lazy-image
Node.js web image engine—Rust (NAPI-RS) core, smaller delivery-oriented outputs vs sharp tradeoffs, mmap / security-first defaults.
I like thinking things through and building what follows—then sharing it as OSS so the work is not locked in one place.
Respect for Albert Einstein.
Rust-first libraries—today via native bindings, with a deliberate road towards WASM on the V8 runtime.
High-throughput image processing pipelines that go beyond default web stacks.
Policy-driven security logic at the edge layer, across multiple cloud providers.
Exploring how AI changes the way we architect, test, and maintain systems.
Node.js web image engine—Rust (NAPI-RS) core, smaller delivery-oriented outputs vs sharp tradeoffs, mmap / security-first defaults.
Policy-first CDN edge security—YAML SSOT, compile to CloudFront / Lambda@Edge / Cloudflare Workers, CI lint & drift checks.
Rust + SWC key extraction and i18next workflows—fast CI, watch mode, optionalDependencies binaries.
Economic CDN cache optimisation — knapsack-based admission, trace replay, and multi-policy comparison ($/period objective).
Treat edge rules like software—especially if you have already stared at WAF knobs while the CDN kept serving traffic untouched.
lazy-image exists so edge-friendly, Rust-first transforms can push global efficiency—not just shave a few kilobytes locally.
If AI ships most code, baseline OSS still leans on a narrowing window for people who practise engineering and curate real foundations—not an exclusive club, but a shrinking one.
AI commoditises syntax. Structure, intent, and constraints matter more than ever.