What will you build with #PHP in 2023?

@phpc Working on a DocBook renderer: https://gitlab.com/Girgias/docbook-renderer

Possibly to improve the php.net docs, but also to have a way to properly write articles on my website (which won't get written but *shhh*)

George Peter Banyard / docbook-renderer · GitLab

GitLab.com

GitLab

@Girgias @phpc Ooo! I worked on such a thing many years ago, in multiple forms.

I take it you don't care for PhD?

@Crell @phpc PhD is an actual nightmare and a massive blob of code that does way too many things.
And none of the people who actually wrote it, don't contribute to it any more since 2012.

Trying to write this in a sane way, but I'm not even sure I can use static analysis on it because of how I overload the DOMNodes :(

@Girgias @phpc I'll take that as a no...

Of course, using it for PHP.Net makes everything harder because of the "no dependencies" rule.

@Girgias @phpc In my experience, some carefully planned xslt really is your friend. If only the docbook-xml tool chain had been updated since 2003...
@Crell @phpc IIRC the point of PhD was to move away from XSLT because those files were unreadable >->
@Girgias @Crell @phpc It was about speed. XSLT took waaaay too long.
@derickr @Girgias @Crell @phpc plus it is not very flexible. Remember a job where they insisted on building an in-house template engine using XLST instead of Twig becease they did not like NIH. Writing templates in it sucked