> If you generate PDFs with headless browsers or HTML-to-PDF tools, you've accepted a compromise: heavy dependencies, memory leaks, and "approximate" layout that shifts across environments Absolutely not true with Prince[0]. It's an HTML/CSS-based typesetter built by the creator of CSS (Håkon Wium Lie [1]) that is lightweight, cross-platform, requires no dependencies, has no memory leaks, is 100% consistent in its ou…
Thanks for the correction. I'm actually not familiar with Prince, so I really can't tell. To be clear, VMPrint isn't meant to compete with established engines like that. It’s just a genuinely helpful tool I built from scratch for the specific tasks I needed to accomplish because I couldn't find an alternative. Prince looks powerful, but I have a feeling it probably wouldn't have been the right fit for my use case any…
Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
31–40 of 64 posts
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#32Do you have a comprehensive integration test suite that can validate the robustness of your implementation?
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#33Interesting! Generating PDFs with properly paginated content is still a pain point in 2026. Do you have a comprehensive integration test suite that can validate the robustness of your implementation?
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#34So this is what it has come to? AI bots writing code and fake origin stories of said code and AI bots commenting on it any other bots responding? This is front page content now? HN: please require all AI generated content to be flagged as such. Ban offenders. This just blows.
I think I'm more tired of AInvestigations than of AI now.
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#35Every single screenshot of Arabic in the README is malformed, the letters are squished together and not connected.
Good eye, you are right. A few others noticed this as well. It is a known trade off given the engine being pure JS and only 80K. The project is still at very early stage, and I'm definitely keeping my eyes open for solutions.
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#36>ai description >ai code >ai comments
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#37>ai description >ai code >ai comments
I wonder what makes AI write its descriptions as puff pieces by default.
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#38Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#39What about these strangely written strange sentences in the README? What does that mean?
> In the 1980s and 90s, serious software thought seriously about pages.
Or this?:
> Desktop publishing software understood widows, orphans, and the subtle difference between a line break and a paragraph break.
As the difference between a line break and a paragraph break is really subtle -could you elaborate a little bit?
Re: Show HN: I built a zero-browser, pure-JS typesetting engine for bit-perfect PDFs
#40>ai description >ai code >ai comments
Why should we presume it’s an AI description? The writing seems reasonable enough. Some people are more naturally inclined towards articulate writing than others (seems like projection) and furthermore the OP claims to be a screenwriter.
I've read a lot of AI generated text and this is definitely one.
However, I also believe in having an objective metric: https://files.catbox.moe/napzf6.png