u/celsowm

I’ve been working on Iridium SQL, an open database engine written in Rust.

The goal is to build a SQL Server-compatible engine and server that works well for application-facing use cases, while also supporting different runtime shapes. Right now the project includes:

a T-SQL engine with a native TDS server
persistent storage by default in native/server mode
WASM support for embedding and browser/local use
a TypeScript client and browser playground

One thing I’m trying to be careful about is compatibility claims: the target is SQL Server compatibility, but I’m not pretending it has full parity. I’m tracking behavior and compatibility explicitly instead of hand-waving it.

Repo: https://github.com/celsowm/iridium-sql

Crates: https://crates.io/crates/iridium_server

I’d really love feedback from Rust folks on the architecture, project direction, API/design choices, and anything that stands out as a good or bad idea.

I’ve been working on pagyra-js, a TypeScript-based HTML-to-PDF library focused on CSS 3 support, font embedding, and browser usage.

Live playground:
https://celsowm.github.io/pagyra-js/

Latest release highlights:

browser/minified bundle published to CDN
compact font subsetting fixed for smaller PDFs
Trusted Publishing via GitHub Actions for release automation

The core render pipeline is stable again and the regression tests are passing.

Repo:
https://github.com/celsowm/pagyra-js
npm:
https://www.npmjs.com/package/pagyra-js

I’d appreciate feedback from people building document/PDF tooling in TypeScript:

API ergonomics
browser bundling approach
PDF size/performance tradeoffs
CSS/layout edge cases worth testing

I built an open SQL Server "clone" in Rust (Iridium SQL)

Pagyra-js: a TypeScript HTML-to-PDF library with browser support and compact font subsetting