dev-setup VS tldr

Something like this at least is the most direct answer to your question, as opposed to "you're doing it wrong" which unfortunately seems to be more upvoted. An example of something like this might be https://github.com/donnemartin/dev-setup

donnemartin - dev setup

A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!

A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.

The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/

Looks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat

a very excellent tool to grab is TLDR https://tldr.sh/

And that's why tldr is such a powerful tool! You can easily install it with sudo apt install tldr or follow this demo.

> ...from the comments section on php.net. The latter was a surprisingly good source but none of this was ever sustainable.

Honestly, I wish more documentation out there had comments/discussion at the bottom.

For example, reading about setting up Open is Connect and having the first (most upvoted) comments on the first page explain things that might not be clear in the docs, analogies that make things easier to understand, or code/configuration snippets for a particular technology.

Somehow the comments in PHP docs were usually like: "after reading the docs, here's what you might want to really know", a bit like those tl;dr apps for manpages: https://tldr.sh/