Feature parity with Cairo? about blend2d HOT 1 OPEN

Not yet, the following features are missing compared to Cairo:

• Operators (on roadmap - low priority, need to check the math about these first)
  • CAIRO_OPERATOR_HSL_HUE
  • CAIRO_OPERATOR_HSL_SATURATION
  • CAIRO_OPERATOR_HSL_COLOR
  • CAIRO_OPERATOR_HSL_LUMINOSITY
• Mesh patterns (not on roadmap)
• Arbitrary clipping to paths (on roadmap, high priority)
• Stroke dashing (API is there, the impl is in progress)
• Cairo push group and pop group - we want a bit different concept here, this won't be 1:1
• Functions like cairo_copy_clip_rectangle_list will not be supported
• Need to check stuff like cairo_mask, etc..

The goal was never to implement full Cairo API, some functions that Cairo exposes are not good for planned multithreaded rendering context implementation (which will be fully asynchronous) like cairo_pop_group() - that's why I have a bit different ideas about implementing layered painting, for example.

I would say that until the API stabilizes it's probably not worth it unless you want to experiment with the provided C-API and provide us some feedback as we are very interested in D and Rust bindings.

from blend2d.