Prince is purpose-built for paged media and non-real-time rendering, so it can make plenty of performance tradeoffs that neither WebKit (and wkhtmltopdf) nor Bl

Prince is purpose-built for paged media and non-real-time rendering, so it can make plenty of performance tradeoffs that neither WebKit (and wkhtmltopdf) nor Blink (and Puppeteer) can, along with having far more engineering resources caring about the paged media case and edge-cases there. It's not cheap, but if you're a publisher I imagine the cost savings of not having to deal with multiple formats (one for print, one for digital) outweighs that many times over, provided you can get good enough results. I do wonder if any publishers will get into the e-reader space, especially on the software-only side. But it's not an easy market to get into and the costs are pretty high, and I think both of us are dubious as to how much any user actually cares.