[xOvni]

Hi, WeasyPrint/pydyf dev here!

> usually a good way to deal with it is to only use a very simple but coherent subset and enforce this usage with validation tools

You’re right, that’s exactly what we do. We support a growing subset of HTML and CSS that’s documented. We also use the W3C testing suite for HTML/CSS, and PDF validators, on top of custom unit tests.

> And big tech is not the only one trying hard to do vendor and developer lock-in.

We "only" follow open specifications and refuse vendor-specific features to avoid lock-ins (equivalent closed-source tools love that). And we even love the other open-source "concurrents": ♥ to Paged.js and Vivliostyle, try them, they’re great too!

[sylware]

"Open" is not enough anymore: it also has to be lean, stable in time, and able to do a good enough _pertinent_ (can be very subjective) job (and in the case of software, that includes the SDK, for instance if some c++ or similar are around, it should be excluded de-facto for obvious reasons).

It is _EXTREMELY_ hard to justify an honnest and permanent income writing software... REALLY HARD.

[pepa65]

How about typst, do you not consider that competition??