I use Linux because I like to know that if my computer doesn’t do what I want, it’s my own damn fault (and not some corporation trying to screw me over).
I use Linux because when I encounter an issue there are numerous helpful forum posts and KB articles that cover it, even for really uncommon glitches. Whereas on Windows for even slightly obtuse errors, you just get the same base-level troubleshooting suggestions and AI listicles. Windows obscures actual useful information from end users which makes troubleshooting issues harder.
Exactly. There’s something reassuring about it always being a skill issue. Am I going to develop those skills? Probably not. But I could.
I actually helped drive someone at my bike co-op to linux by comparing it to why I fix my bike. My bike is janky, but I’m the one who fucked it up. And no irritation is “get over it” it’s “here’s what it would take to fix it, decide if it’s worth it”
I use Linux because I like to know that if my computer doesn’t do what I want, it’s my own damn fault (and not some corporation trying to screw me over).
I use Linux because when I encounter an issue there are numerous helpful forum posts and KB articles that cover it, even for really uncommon glitches. Whereas on Windows for even slightly obtuse errors, you just get the same base-level troubleshooting suggestions and AI listicles. Windows obscures actual useful information from end users which makes troubleshooting issues harder.
cough Canonical cough
I guess it is still “your own damn fault” if you use canonical ‘products’
Exactly. There’s something reassuring about it always being a skill issue. Am I going to develop those skills? Probably not. But I could.
I actually helped drive someone at my bike co-op to linux by comparing it to why I fix my bike. My bike is janky, but I’m the one who fucked it up. And no irritation is “get over it” it’s “here’s what it would take to fix it, decide if it’s worth it”