Don’t take me wrong, there’s some truth to this. But the way it’s written screams “Windows users are drones because of evil Microsoft”. That level of bias is not really constructive. There are more reasonable/rational ways to expand upon this phenemonon that doesn’t end up in a circlejerk. Since it’s quite a big wall of text, I will give one example.
The author makes a broad generalization that, because of Windows’ mystification of its inner workings, Windows users can’t even imagine the thought of becoming a programmer. And well, I know plenty of programmers that to this day have not even touched anything but Windows. Some of them never use the terminal, but some are quite good at it.
My partner got into programming because of learning how to mod games on her Windows PC. The idea that Windows can’t be a path to wanting to program is just a little silly.
And, yet, most of them exhibit this exact behavior: .NET is what Microsoft blesses, and this is the only reasonable language to use.
Don’t get me wrong. There are exceptions; but they are exceptions. And most of those can navigate a Linux terminal reasonably well, even if they prefer Windows.
What the author describes is not learned stupidity, but learned avoidance of diversity. Tell me this doesn’t describe most of the Windows .NET devs you know.
I might need to read it again to be sure but I don’t think that’s what they were saying. I believe they’re talking about something which has been Arch Linux’s philosophy from the beginning which is “know your system”. The process by which you do that is first understanding that Arch is modular and highly configurable. You then choose every component from your Window Manager to your File Manager. The demystification is from you taking the initiative to learn about your options before deciding “I like this one” and then installing it and then configuring it suit your preferences. You don’t have to be programmer to do this, you can follow the ArchWiki or watch SomeOrdinaryGamers install Arch from scratch to a usable system in 45 mins.
The reason the “know your system” philosophy is important is that you, the user, are in control. You are simultaneously the end-user and the sysadmin. You know what you’re installing so if something breaks, there’s this handy terminal to tell you what happened. If that’s not helpful, rollback your changes and try again. Computer too slow? Throw open htop and watch your processes. Trying to kill a stubborn process? F4 to search for it. F9 to bring up the command menu. 9 to select SIGKILL and pres enter.
You’ll probably say “that’s a lot of steps to kill a process” but with routine use, it becomes muscle memory. The more the use it, the more efficient you become at using it.
Your mindset is that if you use any pre-built solution it’s always worse? Do you take this approach to the rest of your life? Do you not eat out ever and cook every meal from scratch, that way if you have a reaction you can eliminate ingredients. That way you know exactly what’s going into your body. Yah that seems like a lot of steps for every meal, but with routine it becomes muscle memory and you get efficient. I’m also assuming you build your own cars.
I mean the concept is silly on its face. It’s not a bad option for people, but it is by no means required. And there is no problem with it. Using a pre built solution is fine. Anyone who has ever worked in tech knows the concept of build vs buy. This falls right into that. Using a best on class black box solution or building your own, there are pros and cons to each.
I’m old enough that it was pretty much a requirement to configure and build your own kernel (2.0 or 2.2, so not that old mind you) among with a ton of other software with linux. Today I’m just happy I can throw an ISO on a USB drive and have a well usable system on a bare metal in less than hour where pretty much everything just works. Since there was so many things that didn’t work until you compiled drivers, wrote configurations and spent hours and hours debugging and testing your solution. Sure, specially back then with a lot less duties for kids and family, the tinkering itself was part of the fun, but today when I just need a system which has tools I need either straight out of the box or after a few apt install’s so that I can get the stuff done I need to I don’t have time nor energy to spend setting up everything.
And with that mindset I could rant quite a lot on why I don’t like the ubuntu installation on my current workstation setup (to be honest, not all of the problems are caused by ubuntu, nvidia has part of the blame and then there’s some poor planning with accessories). I want a system and tools that get out of my way and let me do whatever I need to do instead of requiring continuous TLC or figuring out why some piece of crap from snap doesn’t work anymore.
I’ll offer a balanced position and say nobody can do it all themselves, but I think everyone should strive to be self-sufficient in at least one aspect of modern living. My neighbor grows their own food. My dad is good with cars. My aunt makes quilts and dishware. A society that has crafty knowledge widely distributed like this makes it more likely everyone knows an expert on a given thing, helping prevent people from getting screwed by terrible products. An Arch Linux user might be able to manage linux for 100 close people in their social graph, or at least advocate for it. This also keeps industry from having 100% market share.
That’s quite a hyperbolic conclusion you’ve come to. It’s not that deep and I’m not advocating everyone live their lives by this philosophy.
Remember that Arch Linux is a flavour of Linux and this particular flavour has a particular philosophy. If you want something prebuilt like Windows, there’s Ubuntu, PopOS, Linux Mint, and a myriad of others. You don’t have to go to the level of configuration that Arch does but being Linux, the option is open to you if you wish to dig into your system to see the cogs in motion.
I was basing my stance off the fact that you said the “know your system” philosophy is important, and that we the users should be in control. Which very much could be interpreted as everyone should live by it.
I suppose I could’ve signposted better that I was speaking in the context of Arch Linux but could be applied to any Linux distro. I wasn’t speaking in a general sense just within the parameters of using a PC.
Don’t take me wrong, there’s some truth to this. But the way it’s written screams “Windows users are drones because of evil Microsoft”. That level of bias is not really constructive. There are more reasonable/rational ways to expand upon this phenemonon that doesn’t end up in a circlejerk. Since it’s quite a big wall of text, I will give one example.
The author makes a broad generalization that, because of Windows’ mystification of its inner workings, Windows users can’t even imagine the thought of becoming a programmer. And well, I know plenty of programmers that to this day have not even touched anything but Windows. Some of them never use the terminal, but some are quite good at it.
My partner got into programming because of learning how to mod games on her Windows PC. The idea that Windows can’t be a path to wanting to program is just a little silly.
Made my way to CTO and it all started by making WoW mods on my PC in high school. I don’t get that mindset at all. Hell I still program on windows.
And I did too because I wanted to make EPIC minecraft servers back in 2010 :)
And, yet, most of them exhibit this exact behavior: .NET is what Microsoft blesses, and this is the only reasonable language to use.
Don’t get me wrong. There are exceptions; but they are exceptions. And most of those can navigate a Linux terminal reasonably well, even if they prefer Windows.
What the author describes is not learned stupidity, but learned avoidance of diversity. Tell me this doesn’t describe most of the Windows .NET devs you know.
I might need to read it again to be sure but I don’t think that’s what they were saying. I believe they’re talking about something which has been Arch Linux’s philosophy from the beginning which is “know your system”. The process by which you do that is first understanding that Arch is modular and highly configurable. You then choose every component from your Window Manager to your File Manager. The demystification is from you taking the initiative to learn about your options before deciding “I like this one” and then installing it and then configuring it suit your preferences. You don’t have to be programmer to do this, you can follow the ArchWiki or watch SomeOrdinaryGamers install Arch from scratch to a usable system in 45 mins.
The reason the “know your system” philosophy is important is that you, the user, are in control. You are simultaneously the end-user and the sysadmin. You know what you’re installing so if something breaks, there’s this handy terminal to tell you what happened. If that’s not helpful, rollback your changes and try again. Computer too slow? Throw open htop and watch your processes. Trying to kill a stubborn process? F4 to search for it. F9 to bring up the command menu. 9 to select SIGKILL and pres enter.
You’ll probably say “that’s a lot of steps to kill a process” but with routine use, it becomes muscle memory. The more the use it, the more efficient you become at using it.
Your mindset is that if you use any pre-built solution it’s always worse? Do you take this approach to the rest of your life? Do you not eat out ever and cook every meal from scratch, that way if you have a reaction you can eliminate ingredients. That way you know exactly what’s going into your body. Yah that seems like a lot of steps for every meal, but with routine it becomes muscle memory and you get efficient. I’m also assuming you build your own cars.
I mean the concept is silly on its face. It’s not a bad option for people, but it is by no means required. And there is no problem with it. Using a pre built solution is fine. Anyone who has ever worked in tech knows the concept of build vs buy. This falls right into that. Using a best on class black box solution or building your own, there are pros and cons to each.
I’m old enough that it was pretty much a requirement to configure and build your own kernel (2.0 or 2.2, so not that old mind you) among with a ton of other software with linux. Today I’m just happy I can throw an ISO on a USB drive and have a well usable system on a bare metal in less than hour where pretty much everything just works. Since there was so many things that didn’t work until you compiled drivers, wrote configurations and spent hours and hours debugging and testing your solution. Sure, specially back then with a lot less duties for kids and family, the tinkering itself was part of the fun, but today when I just need a system which has tools I need either straight out of the box or after a few apt install’s so that I can get the stuff done I need to I don’t have time nor energy to spend setting up everything.
And with that mindset I could rant quite a lot on why I don’t like the ubuntu installation on my current workstation setup (to be honest, not all of the problems are caused by ubuntu, nvidia has part of the blame and then there’s some poor planning with accessories). I want a system and tools that get out of my way and let me do whatever I need to do instead of requiring continuous TLC or figuring out why some piece of crap from snap doesn’t work anymore.
I’ll offer a balanced position and say nobody can do it all themselves, but I think everyone should strive to be self-sufficient in at least one aspect of modern living. My neighbor grows their own food. My dad is good with cars. My aunt makes quilts and dishware. A society that has crafty knowledge widely distributed like this makes it more likely everyone knows an expert on a given thing, helping prevent people from getting screwed by terrible products. An Arch Linux user might be able to manage linux for 100 close people in their social graph, or at least advocate for it. This also keeps industry from having 100% market share.
That’s quite a hyperbolic conclusion you’ve come to. It’s not that deep and I’m not advocating everyone live their lives by this philosophy.
Remember that Arch Linux is a flavour of Linux and this particular flavour has a particular philosophy. If you want something prebuilt like Windows, there’s Ubuntu, PopOS, Linux Mint, and a myriad of others. You don’t have to go to the level of configuration that Arch does but being Linux, the option is open to you if you wish to dig into your system to see the cogs in motion.
I was basing my stance off the fact that you said the “know your system” philosophy is important, and that we the users should be in control. Which very much could be interpreted as everyone should live by it.
I suppose I could’ve signposted better that I was speaking in the context of Arch Linux but could be applied to any Linux distro. I wasn’t speaking in a general sense just within the parameters of using a PC.