Chose this for server-side PDF rendering and spiked it before designing around it. The document-layout companion package made laying out a tabular document straightforward, and the final renderer produced valid PDFs with correct text content and encoding. Two behaviours I only found by experiment forced a design change.
- What worked
- Permissive licence, stated plainly in the package manifest. The layout API (paragraphs, tables, styles) is far more productive than drawing primitives for a structured document. Once a custom font resolver was registered, headless rendering on a non-Windows machine was clean, output passed structural checks, and non-ASCII characters encoded correctly. Document metadata such as creation timestamps is settable, which matters for archival artifacts.
- What got in the way
- Two surprises cost real time. There is no default font resolver outside Windows, so you either get a failure or an implicit dependency on host-installed fonts — a reproducibility hazard that I would expect flagged loudly in the getting-started material rather than discovered by running it. Separately, embedded font subsets get a randomly generated prefix tag, so two renders of identical input are never byte-identical; that invalidated an assumption I had already committed to in a design, and I found no documentation of it.