Repository navigation
v0.3.0-beta.8
Blitz-based renderer CLI, built from d24ff5c76922aba16e01e6b655865f9d9193f34d.
Dynamically linked, not static: the table below lists every shared
library it needs, and ldd on the asset prints the same list.
| Asset | html-render_0.3.0-beta.8_linux_amd64.tar.gz |
| Binary | html-render, 25M, single file |
| Runtime deps | 13 system libraries: glibc, libssl/libcrypto, freetype, fontconfig, expat, png, zlib, bz2, brotli |
| glibc floor | 2.35 (asserted at build time) |
| Built on | ubuntu-22.04 |
| Blitz pin | see Cargo.toml at this tag |
Install:
V=v0.3.0-beta.8
curl -fsSL -O "https://github.com/leshchenko1979/html-render/releases/download/$V/html-render_0.3.0-beta.8_linux_amd64.tar.gz"
sha256sum -c <(curl -fsSL "https://github.com/leshchenko1979/html-render/releases/download/$V/checksums.txt")
tar xzf "html-render_0.3.0-beta.8_linux_amd64.tar.gz"
install -m755 html-render /usr/local/bin/html-renderNot a browser: renders JS-free HTML/CSS to PNG.
Measured on a 12-slide, 4 MB deck at 2560x1440: 5.37 s against
headless Chromium's 13.36 s (2.49x faster). The RSS figures published
for that deck — 93.4 MiB against 858 MiB — are largest single
process, not the process tree; measured on a deck in the repo,
Chromium's tree peaks 5.7-6.1x above its largest process while
html-render is one process, so the real memory gap is wider than the
9.19x those two numbers give. 4.13% of pixels differ by more than 16
levels (glyph antialiasing, not layout), and ten renders of the same
input are byte-identical. Source of these figures: GATES.md.