As you've pointed out, there are two active projects in Asciidoctor that provide a PDF converter, though with very different approaches. And yes, we communicate. I currently lead Asciidoctor PDF and Guillaume leads Asciidoctor Web PDF. We communicate every day.

The reason there are two converters is because we've reached (or very nearly reached) the limit of what we can do with Asciidoctor PDF. The hope is that Asciidoctor Web PDF can sail over these limitations and thus eventually replace it. Though, given how much functionality is in Asciidoctor PDF, that's still a very tall order. (PDF is very, very difficult to make). So the effort to get there is ongoing.

My plan is to announce this strategy, and address the relationship between the two projects, after I release Asciidoctor PDF 2.0.0. However, that release has been held up due to technical challenges finalizing several remaining enhancements that are slated for it.

If Asciidoctor PDF works for you, and its limitations aren't prohibitive, then you can keep on using it. However, if it's not working for you, I encourage you to evaluate Asciidoctor Web PDF as an alternative. Feedback is only going to make it better.

To build on what David wrote:
> I think everyone agrees that the asciidoctor-web-pdf approach is “the future” of pdf rendering, but it’s difficult to predict when it might become as reliable as asciidoctor-pdf.

We do hope that Asciidoctor Web PDF can give us a better way to make highly customized PDFs, but it's still too early to predict if that will prove possible. It's certainly showing promise!

Best Regards,

-Dan