I feel the criticism is valid because most parsers in production are done via hand without tooling or fancy techniques.
I don't see why you say that, parser combinators are just a structured way to compose recursive descent parsers, you can do everything with them that you can with any other hand-rolled parser. You don't even need to construct an AST at all, a mathematical expression "parser combinator" could just return a single number, the result of evaluating the expression.
What? Do you have any data you'd like to share?
I'm given to understand that e.g. the C++ compilers usually have a hand-coded, but AFAIUI that's mostly due to the complexity of actually parsing it (and fitting that into anything other than just raw code).
https://www.drdobbs.com/architecture-and-design/so-you-want-...
A common theme is that the parser generator does not provide you the tools to write the high quality error messages. Having used ANTLR and other tools, I believe it now that I'm trying to ship a real language.
(IME MegaParsec basically solves most of the issues.)
Failed to parse!
While: parsing a numberWhile: parsing addition expression
While: parsing a mathematical expression