I would say, put that famous book in the docs and see what happens. I would expect a positive outcome. Am I right chromatic ?

The core documentation has enough problems without another 70,000 words added to it.

I wrote the book and deliberately skipped some features, argued against using others, and ignored the entire default OO system in favor of Moose (before explaining the default object system as something you might have to maintain). It's one way to learn to write Perl 5 effectively. I hope it's useful for people, but it's certainly not the only way.

(Also I'd hate to have to debate stylistic choices on p5p before updating it for a new version.)

How about writing another free book on Extending and hacking perl to encourage more people to work on Perl ecosystem itself. I know there is core hackers project but that there just as portal for some links. We need a good book which goes into details of all that stuff.

Rather than a whole book, a few SWIG articles less than 13 years old would be nice. Both SWIG and Perl have changed a bit since then.

that's because the documentation is bulky sometimes

Besides, if the problem is bulky documentation, adding an entire book isn't reducing that problem.

I would say, put that famous book in the docs and see what happens.

Am I right chromatic

Chromatic doesn't seem the most objective person to ask about it.

Nobody's objective. So what?

---

Improve your skills with Modern Perl: the free book.