Skip to main content
Image

r/rust


Mellow - a fully-featured & minimal local music player for Linux (GStreamer + GTK + Rust)
Mellow - a fully-featured & minimal local music player for Linux (GStreamer + GTK + Rust)
🛠️ project
Image r/rust - Mellow - a fully-featured & minimal local music player for Linux (GStreamer + GTK + Rust)

slopc: a proc macro that replaces todo!() with LLM-generated code at compile time. I am not sorry.
slopc: a proc macro that replaces todo!() with LLM-generated code at compile time. I am not sorry.
📸 media
Image r/rust - slopc: a proc macro that replaces todo!() with LLM-generated code at compile time. I am not sorry.

A pure-Rust HTML/CSS/Markdown to PDF converter, way faster than headless chrome
A pure-Rust HTML/CSS/Markdown to PDF converter, way faster than headless chrome
🛠️ project

Hello y'all! We are very happy to be shipping this little project to production, a small Rust library that renders HTML directly to PDF, faster, very much faster!

Today, most PDF generation relies on headless Chromium. It works, but at a cost:
- 500MB+ of memory per instance
- Hundreds of ms of cold-start and process IPC
- Doesn't run on Cloudflare Workers, Vercel Edge, or in the browser

This project is an embeddable Rust crate with no Chrome subprocess, no headless browser, no 300MB binary blob shipped with your app. It also compiles to WASM, so the same renderer runs server-side, at the edge, or entirely in a user's browser.

Where it unlocks value:
- SaaS at scale: invoices, contracts, receipts, shipping labels. Per-request PDF for a fraction of the Chromium cost.
- Edge & serverless: PDF on Workers, Lambda, Deno Deploy, Fastly. Places Chromium simply can't go.
- Privacy-first features: generate PDFs client-side in WASM. User data never leaves the browser.
- ML & LLM agents: fast enough to be a real tool in an agent loop, cheap enough to synthesize training datasets for document-understanding models.
- Deterministic output: same HTML, same bytes. Useful for hashing, diffing, and snapshot testing.

The moat we're building is a live parity dashboard comparing our lib against Chromium page by page as we believe "Chrome-quality output without Chrome" only means something if we can get closer to it every commit. A simple playground is also available.

Still a little way to go before hitting lower chromiums parity, hence, all contributions / feedback / issues welcome!

Have a great day