The great thing about Linux is if something has weird behavior and you’re already exhausted all possible options to solve it, it is still possible to figure it out on your own because the source code is available.
I still don’t know how windows people figure out how to fix such and such problems on windows with some registry entries. Did they ask a Microsoft employee, or did they mess around with the registry blindly until it’s magically fixed?
Not everyone is a developer, but the vast majority of people use Windows. When an issue arises, it’s easier for a non-programmer to search for help than look at code.
Sure, you also have that option on Linux, which would be the first thing you do anyway. But after you searched everywhere and found nothing, on Linux you still have an option to dig into the source code yourself, while on windows you’re pretty much done unless you have a support contract with ms.
When an issue arises, it’s easier for a non-programmer to search for help than look at code.
Ahh, look! Its my nearly decade long experience with Linux in one sentence! So that whole non-user-friendliness thing about Linux being uncomprehensible to amateurs, that’s surely just around the corner for me now, right? Right?!
Not trying to argue any point here, ur comment in this context just made me chuckle.
I’m not a super casual user, but there’s no way in hell I’m going to try to dive into source to try to understand a bug in my OS. I’m just going to work around it and never think of it again.
You may feel that way, but not every power user is like you. Linux distro is not a monolith, it’s made up of thousands of small components made by different people and organizations. If you look at some of those components source control (e.g. on GitHub or GitLab), you’ll see a large portion of pull requests are done by their users who found bugs and decided to submit a fix themselves. For example, just look at how many pull requests libgweather got, and they’re mostly submitted by gnome users who were mildly annoyed with the weather app.
It is actually easier than you think. With the help of the devs, you could easily solve your problem, plus make them aware of the bug and fix it in upcoming releases. It might take a few days of messages on git back and forth with them, but in the end, yes, you will most probably solve your problem.
No, you Google the shit out of that particular problem, visiting reddit, forums, blogs and god knows what else, find a few bunch of registry files or reg snippets, copy/paste that, do a sanity check on each and every one of them, backup the registry (or a part of it at least), import them one by one in the hope that one of them fixes the problem… and then you discover that these were meant for Windows 7 and not 10 and that 10/11 had that shit removed or doesn’t actually obey that registry entry (a bug, they will fix it… some day…) and then just give up and learn to live with the problem.
The great thing about Linux is if something has weird behavior and you’re already exhausted all possible options to solve it, it is still possible to figure it out on your own because the source code is available.
I still don’t know how windows people figure out how to fix such and such problems on windows with some registry entries. Did they ask a Microsoft employee, or did they mess around with the registry blindly until it’s magically fixed?
Not everyone is a developer, but the vast majority of people use Windows. When an issue arises, it’s easier for a non-programmer to search for help than look at code.
Sure, you also have that option on Linux, which would be the first thing you do anyway. But after you searched everywhere and found nothing, on Linux you still have an option to dig into the source code yourself, while on windows you’re pretty much done unless you have a support contract with ms.
Ahh, look! Its my nearly decade long experience with Linux in one sentence! So that whole non-user-friendliness thing about Linux being uncomprehensible to amateurs, that’s surely just around the corner for me now, right? Right?!
Not trying to argue any point here, ur comment in this context just made me chuckle.
I’m not a super casual user, but there’s no way in hell I’m going to try to dive into source to try to understand a bug in my OS. I’m just going to work around it and never think of it again.
You may feel that way, but not every power user is like you. Linux distro is not a monolith, it’s made up of thousands of small components made by different people and organizations. If you look at some of those components source control (e.g. on GitHub or GitLab), you’ll see a large portion of pull requests are done by their users who found bugs and decided to submit a fix themselves. For example, just look at how many pull requests libgweather got, and they’re mostly submitted by gnome users who were mildly annoyed with the weather app.
It is actually easier than you think. With the help of the devs, you could easily solve your problem, plus make them aware of the bug and fix it in upcoming releases. It might take a few days of messages on git back and forth with them, but in the end, yes, you will most probably solve your problem.
No, you Google the shit out of that particular problem, visiting reddit, forums, blogs and god knows what else, find a few bunch of registry files or reg snippets, copy/paste that, do a sanity check on each and every one of them, backup the registry (or a part of it at least), import them one by one in the hope that one of them fixes the problem… and then you discover that these were meant for Windows 7 and not 10 and that 10/11 had that shit removed or doesn’t actually obey that registry entry (a bug, they will fix it… some day…) and then just give up and learn to live with the problem.
They pay for books any expensive classes. I Boomer IT culture talent comes with money and age.
Source: Rejected several tiles for being too young to reasonably know Linux.