[kweingar]

I wouldn't manually write documents in groff these days, but I have found that it can still be useful for automatically generated PDF reports/documents.

Groff is lightweight and already installed on most Linux systems, and the build process is way cleaner than TeX. It's easy to make a Python script that reads some data and prints a nice-looking report (or a form letter, etc.)

[rleigh]

Yes, integrating it into a scripted workflow, including dependency-based build systems, is vastly easier. The multiple runs of TeX don't fit well into this model, and the Unix heritage of troff vs the TeX is clearly apparent in the design, which permits all the bits to be piped together. It's clearly dated and limited in many ways, but it's still extremely powerful, and it can do automated document generation very well. I've used it for this in the past, and would recommend it.

While we do have more modern stuff like Markdown and ReStructured Text, these are in their own way extremely limited and are primarily focussed upon transformation to HTML. troff is focussed upon printing, and if you want nice PDF reports, and you don't want the slowness and excessive disk space consumption of TeX, it can be an excellent solution.

[nonrandomstring]

> still extremely powerful, and it can do automated document generation very well.

These days I am more likely to be working in org-mode and using elisp snippets to automate stuff, but roff is a solid fallback for things like quickly turning 100 paragraphs of individual feedback into 100 formatted pdf documents that can be mailed out.