Thank you. This industry has a huge failure mode in touting tech used in projects/frameworks without linking out to at least the source so that someone can learn about them. Can't tell you how many things I've bailed on because it was a pile of obscure library references that weren't (to me) worth looking up.

Indeed, there is a skill when doing technical writing of putting yourself in the position of a reader, particularly one who is competent but who doesn't already know the thing that you are trying to explain, or the context. It's not as common as it should be.

To be fair, in this case the linked page is a subdirectory of the main Puppeteer project.

This is also an experimental project. Who here thoroughly documents their experiments? Although to be fair we did announce it at I/O so that calls for more documentation.

Disclosure: Chrome DevTools docs guy

I always find it weird that people constantly try to "sell" me (us) something but never tell me what that thing is or why I want it.

I can only assume that anyone who submits "Puppeteer for Firefox" or "x for y" to Hackernews, is someone who works daily with Puppeteer / x and has the necessary context and doesn't notice that it's not aimed at a more general audience (1).

Then it gets upvoted to a more general audience, who ask "Puppeteer? what's that?"

1) https://news.ycombinator.com/item?id=20507728