Since webrender is now the default renderer, and is being tested on CI,
what should we do with the Azure/Moz2D related code in layout / gfx /
compositor?
The options are:
1) Fully maintain the Azure rendering path - run CI builds against both
Azure and Webrender.
2) Leave the Azure rendering code intact, but don't run tests against it
(semi-maintained).
3) Remove the Azure rendering code path.
Some points for/against each option:
(1) may help with printing support (via one of the PDF backends for
Moz2D), but adds extra maintenance burden (different test expectations,
extra work when adding new features).
(2) is likely to bit-rot fairly quickly.
(3) simplifies current work going forward, but doesn't help out with
printing / pdf output. Means that everyone working with Servo must have
GL3+ compatible hardware (although you can run llvmpipe software
rendering as required).
My preference is to remove the azure code from git - it seems unlikely
we'll be working on printing any time soon, and we will always have the
history in git.
Thoughts or other suggestions?
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
