In demonstrating one of the gaps of man pages in modern times and likely having hindered the adoption of the Linux kernel's new mount API, it took more than six years for those system calls to be properly documented within man pages. The Linux "new" mount API was introduced back in mid-2019 with Linux 5.2 and since supported by key file-systems after several years but not until weeks ago was this file descriptor based mount API scoped out within man pages.
The "new" mount API for Linux is a set of system calls like fsopen and fsconfig for offering more flexibility than the Linux kernel's long-used mount system call that is a one-shot approach compared to this modern multi-step design for better flexibility. In the kernels since Linux 5.2, various file-systems have transitioned to supporting the modern mount API. It was only earlier this year that F2FS added support for it as one of the last major file-systems without it.
Groff is indeed such a crap format to write documentation in. It nearly reads like zalgo.
I can't wait for the anti markdown people to come out of the woodwork though and complain that it's "the progressivist agenda" to be more user friendly because devs aren't users.
"If you can't write Groff, maybe you dont deserve to read the output"
"The markdown evangelists are so annoying. You can't just rewrite everything in markdown"
"When will this markdown craze stop??? I can't hear it anymore!"
Identity politics entered the developer arena.
My personal bias is being pro markdown. I do not know groff so below is based on some inferences on my part.
But I don't think markdown is suitable for man pages, which contain specific kinds of information structured in a prescribed way. Markdown doesn't and can't know about these.
As I understand it, because of using a more sophisticated structure than MD, its possible to do things like: