I'm not accusing anyone. I'm not demanding that this be fixed. I am merely stating that these things are the difference, between me, a somewhat technically minded person being able to plopp a linux distro on my grandpa's PC and tell him "just look for the help button and go from there". ...and not being able to do that.
The difference can be a simple "let me google that for you" button. It can be a manual, but then the manual should be complete and translated, which is always tough. It can also be a disclaimer that says "look, this is experimental, thanks for using it, if you have problems write me an email at ... or leave message on github/mastodon/facebook/linkedin".
The things it should not be: obscure or require meta knowledge to even find. This applies to console commands as well. "ls" and "cd" work fine, but if the target person hasn't receieved some kind of hand holdy experience as an introduction to linux or the command line, they will be helpless here is as well.
Setting personal emotions aside, this is your customer:
linux devs are either stuck in details or they are treating software as a personal project and don't think from a users perspective most of the time. What do I mean by that? Well, let's take blender. Blender has a "help" menu that looks like this:
This is good,
the links to community, documentation and finally bug reporting are there and are reasonable.
The "user settings" option in the settings subsection that comes with my xubuntu distro also has a "help" button. Which opens a manual page that looks like this:
that's not a loading bug. Or maybe it is, anyway, it stays like that. Empty.
This is the volume control:
Do you see any help here? No? Me neither. A link to a manual? So, suppose you have a problem, how do you even search for it? Because all you know is that it's "volume control" and "on my linux distribution".
And this is the easy, simple stuff. This is the "let's turn on my machine and listen to some music on youtube" level of complexity.
This is the snap store:
What is making me slightly angry is the sheer arrogance:
"my software is so perfect, so obvious, the user will never need help, there will never be a bug, so there doesn't need to be a bug report button. It is so obviously the most bestest software, that the user doesn't need to know who made it, how to turn it off, and they most certainly will never need to know how it works. It will never break, so it will never need to be repaired, it's perfect, so nobody will ever want or need a replacement."As long as this attitude persists, I will recommend linux begrudgingly, as a lesser evil. If someone complains that linux is not for them, I won't correct them. Because this stuff sucks, it's a problem and they may be completely right.
let's take this as a source for some distros https://distrowatch.com/
Let's say you do find a bug. Let's say you even find the organisation who made the software, the correct forum or bug tracker or whatever. None of the major bug tracking system have any kind of metric to judge how fast you can expect help.
Anyone can file bugs: All users are encouraged to file any bugs they run into. Bug filing is not limited to only software developers.Which is an arrogant, bold faced lie. You dont' want that. Regular users don't want that either.
The irony is alive and well of course, because the rest of this docs page is pretty good. In fact, it's good enough to be a general guide to reporting bugs anywhere, excluding some platform specific individual advice and how to's about using e.g. bugzilla.
Basically, this is developer land.
Which is fine, of course.
But you really shouldn't be surprised that a normal user (read hank hill), being foreign to it, will feel excluded and not wanting to parcitipate in it.