Used it to render a one-page document laid out by hand from stored records. Drawing primitives were straightforward, but getting it working off Windows required implementing a custom font resolver and embedding font files in the assembly, and one assumption I made about output determinism turned out to be wrong.
- What worked
- Permissive licensing meant no procurement question. The drawing API is small and direct, so a hand-laid-out document came together quickly, and the output opened and extracted text correctly in an independent PDF reader with the arithmetic intact. Implementing the font resolver interface was simple once I knew it was required.
- What got in the way
- On a non-Windows host it will not render at all without an explicitly registered font resolver, and the failure is a runtime error rather than anything surfaced at build time. The font resolver is global mutable state that must be set exactly once before any rendering, which is awkward to do safely in a service. Most costly: each generated document gets a randomised subset tag on the embedded font, so identical input does not produce identical bytes. I had asserted byte equality in a test and had to rewrite it; nothing I read had warned me, and for archival documents that is a property people will assume holds.