WKHTMLToPDF VS twirp

We’ll start with the WickedPDF gem, which is powered by the wkhtmltopdf command-line library.

The only “sane” way I’ve found to be able to deal with pdfs is through this tool https://wkhtmltopdf.org/

wget + https://wkhtmltopdf.org/

Thanks for the suggestion! KnpSnappyBundle was my initial way to go as well, but my pages use quite some Javascript (chartJs) to render and I couldn’t get wkhtmltopdf to work with it. As it seems wkhtmltopdf does not support ES6 https://github.com/wkhtmltopdf/wkhtmltopdf/issues/3596 so I was forced to find another way.

wkhtmltopdf — Generates PDFs from HTML documents.

Of the HTML-based pdf-engines pandoc supports, prince would have the best typography, but I don't like recommending Prince because it's proprietary and costs money. (I try to stick to open source when I can.) wkhtmltopdf is the fastest, but uses a pretty old codebase, and doesn't even support paged/print css. weasyprint is a little better in my experience, but still has a ways to go typographically. pagedjs-cli is just a wrapper around headless Chrome/Chromium, and while Chrome has made improvements with regard to typography, Google turns off some of those features (e.g., hyphens) in headless mode, which is annoying.

Concerning pdf there is the well known wkhtmltopdf , but let me say that I love the not so well known percollate

Did you try wkhtmltopdf and WeasyPrint, by any chance?

Since the srd uses standardized links (base/creature type/creature name) you could make a list of urls based on your selected monsters in a spreadsheet, then use a program like https://wkhtmltopdf.org/, https://www.weenysoft.com/free-html-to-pdf-converter.html, or the url conversion feature in Adobe Acrobat Pro if you combine all the urls into an htm for Acrobat to pull from.

The next time I want to build an API, I will probably make use of https://github.com/twitchtv/twirp. I like working with Protobuf and having strongly-typed and well-defined messages, but gRPC is way, way too much. It's obviously a Google product, built for what Google needs.

Use Protobuf for messages, but just use HTTP for transport.

- Twirp (Twitch light version of gRPC, with optional JSON encoding, HTTP1 support and without streaming) - https://github.com/twitchtv/twirp

There is another: twirp

And addition to what was mentioned there are also webrpc and twirp.

If you find one, you maybe also interested in twirp.

Twitch has a great framework for it https://twitchtv.github.io/twirp/docs/intro.html

We have better experience with https://goa.design/ than with https://github.com/twitchtv/twirp

Take a look at Twirp (https://github.com/twitchtv/twirp) open sourced by TwitchTv. It's a lot lighter weight than gRPC. It does use Protobufs but addresses some of the concerns you mentioned, such as being able to test with JSON payloads, works over HTTP 1.1 and HTTP/2, good client libraries, and doesn't require a proxy.

They address your concerns in more detail in the Twirp release announcement (2018) - https://blog.twitch.tv/en/2018/01/16/twirp-a-sweet-new-rpc-f...