Accessibility of information has also caused a problem of academic rigour getting removed with the higher barrier cost of learning curve.
At least now I can just ask a question and get a decent answer without needing to dig through manuals that leave me more confused than before or going the roundabout route of saying “Linux sucks, you can’t even do thing on it” and waiting for someone to correct me with a painstakingly detailed explanation.
We might have to come up with ways of curating answers or making that curated content more accessible too, but until we have a universal linux advice chatbot that can answer natural language questions and clear up nuance, people will keep asking questions on public forums.
Google can’t understand all nuances of the question and latches on to keywords instead. If I search for “Thing does not work in context”, I get answers for how to do thing in context, but not what to do to troubleshoot it if it refuses to show me any decent error message (or doesn’t produce an error, simply unintended results running counter to every one of those answers, including the fucking manual, which I did read thoroughly, several times).
At least now I can just ask a question and get a decent answer without needing to dig through manuals that leave me more confused than before or going the roundabout route of saying “Linux sucks, you can’t even do thing on it” and waiting for someone to correct me with a painstakingly detailed explanation.
We might have to come up with ways of curating answers or making that curated content more accessible too, but until we have a universal linux advice chatbot that can answer natural language questions and clear up nuance, people will keep asking questions on public forums.
Google can’t understand all nuances of the question and latches on to keywords instead. If I search for “Thing does not work in context”, I get answers for how to do thing in context, but not what to do to troubleshoot it if it refuses to show me any decent error message (or doesn’t produce an error, simply unintended results running counter to every one of those answers, including the fucking manual, which I did read thoroughly, several times).