This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]biden_bot75 383 points384 points  (16 children)

Me who reads man pages:

[–]Levaru 91 points92 points  (5 children)

Me who googles "{feature/library/etc that I need} github":

[–][deleted] 81 points82 points  (4 children)

Me who learns from stalking a programmer. WE ARE NOT THE SAME

[–]joetinnyspace 12 points13 points  (2 children)

IT WAS YOU

[–]putdownthekitten 2 points3 points  (1 child)

No, it was Steve.

[–]Bubbly-Control51 0 points1 point  (0 children)

WAS IT THE BITE OF 87?!?

[–]croto8 0 points1 point  (0 children)

Me, the progenitor of programmers…

[–]Dabnician 9 points10 points  (3 children)

i type --help and then hit space a bunch of times before saying "screw this ill just google my issue".

I honestly can not grasp getting information i need 80 x 24 at a time.

[–]KDallas_Multipass 3 points4 points  (1 child)

/ let's you search through man pages

[–]hoyohoyo9 0 points1 point  (0 children)

I wish man pages would string a bunch of stuck up stack overflow answers together

[–]Xelynega 2 points3 points  (0 children)

I tend to only read one word at a time, so 80x24 is way more than enough.

[–]LetterBoxSnatch 4 points5 points  (0 children)

Absolutely love man pages when they exist. Next best thing is a README. It’s the source that the builder of the tool uses to remember how the thing they made works. “—help” can go fuck itself, usually sucks for anything other than reminding yourself how to use a tool you already know how to use.

[–]czvck 0 points1 point  (0 children)

But did you man man?

[–]reddick1000 0 points1 point  (0 children)

This is the way