> I think it's really valuable having a conversation partner with infinite patience for explaining things
This is what keeps me coming back. So much knowledge is just unapproachable because of the domain-specific semantics used, even in introductory/help contexts. From the opening text of the man page for "cat," arguably the most basic command in Linux:
> By default, sparse SOURCE files are detected by a crude heuristic and the corresponding DEST file is made sparse as well. That is the behavior selected by --sparse=auto. Specify --sparse=always to create a sparse DEST file whenever the SOURCE file contains a long enough sequence of zero bytes. Use --sparse=never to inhibit creation of sparse files.
I've been using Linux for 20 years and have no idea what the fuck any of this means. Slapping an "ELI5" prefix on it and feeding it to GPT makes this stuff intelligible, even if it's wrong (for unfamiliar concepts about not-code, I'll ask the same question three different ways and see if/how much it differs).
This is what keeps me coming back. So much knowledge is just unapproachable because of the domain-specific semantics used, even in introductory/help contexts. From the opening text of the man page for "cat," arguably the most basic command in Linux:
> By default, sparse SOURCE files are detected by a crude heuristic and the corresponding DEST file is made sparse as well. That is the behavior selected by --sparse=auto. Specify --sparse=always to create a sparse DEST file whenever the SOURCE file contains a long enough sequence of zero bytes. Use --sparse=never to inhibit creation of sparse files.
I've been using Linux for 20 years and have no idea what the fuck any of this means. Slapping an "ELI5" prefix on it and feeding it to GPT makes this stuff intelligible, even if it's wrong (for unfamiliar concepts about not-code, I'll ask the same question three different ways and see if/how much it differs).