I’ve got to confess, I have for years been guilty if not reading the documentation. I simply go with the flow and hope it works…

But not anymore! And why the change you may ask? We’ll, I’m reading the f…ing documentation on Rocky linux and I’m just blown away from the amount of great information!

If you’ve been guilty of not reading the documentation, let me me know what changed it for you

If you’re not reading the documentation, this is your time to confess!

  • PerogiBoi@lemmy.caEnglish
    61·
    9 hours ago

    In my experience, all the Linux documentation I have read has been written for peers of Linux developers, who are familiar with technical terminology and several concepts and steps are left out and implied rather than explained.

    It’s a way for developers to ensure that Linux never receives adoption past other developers. Literary equivalent of pulling the ladder up.

    • Xanza@lemm.eeEnglish
      1·
      1 hour ago

      I mean, it’s technical documentation. There’s a limit to how exciting it can be. lol.

    • Psychadelligoat@lemmy.dbzer0.comEnglish
      2·
      8 hours ago

      who are familiar with technical terminology and several concepts and steps are left out and implied rather than explained.

      Said it before and I’ll say it again: had to manually install some software to make Steam tinker launch work, and the instructions for installing it were to download and prepare the GitHub folder, then “do the usual and move the completed file to …”

      Ive used git in the past and it still took me multiple minutes to figure out they meant the “make && build” command. Why was that so hard to fucking write??