Set up a Windows folder share for use on the Linux device within your home network.
Set up a Windows folder share for use on the Linux device within your home network.
There’s no single best operating system. Each has its own advantages depending on how it’s used. My mistake was attempting to apply an IOT or server OS to a desktop setup. In Linux, installing software follows a clear process: search official repositories, check flatpack sources, and if needed, download precompiled packages from vendors—something I had to do when using VMware for remote access. This method is straightforward and reliable in Linux. Compared to Windows, it’s even more convenient because updates are typically handled automatically.
I prefer the graphical interface over command lines. With so many situations, I rely on visual cues instead of typing commands manually. For clarity, I don’t need to remember exact names or versions; I learn quickly and study extensively. My goal is to focus on practical tasks rather than mastering CLI. I’m preparing for a licensing exam soon, which makes me realize that most people concentrate on GUIs, not CLI—even when they have licenses.
I’ve explored Linux and terminal manuals in the library, but I find them unappealing. The idea of needing different commands across distros is frustrating. While I appreciate some Linux users who think a small market share equals intelligence, I believe using better tools is smarter. Most people aren’t interested in learning OS operations; they want to use their preferred software. Software itself is usually GUI-based—whether it’s a browser, accounting program, or CAD tool. Even ATMs don’t expose CLI to users.
I haven’t heard much about CLI-powered tablets or iPhones. If we count all user-facing devices, GUIs clearly dominate. True CLI use is reserved for experts who deeply understand their tasks—rare among everyday users. I wonder if asking ChatGPT what to do would help clarify the value of CLI versus GUI. For now, I stick with Linux on secondary machines for media or backup, while keeping Windows for my main office PCs. I’m open to switching, but my current setup balances flexibility and usability.
Hardware-wise, upgrading from a W11 to Linux is manageable, so I can adapt easily. I don’t see a need to go all-in on Mac yet, as it would be a significant leap and could introduce new issues. Linux is a great way to repurpose older PCs.
ok so firstly you are right that we shouldnt paste random commands from the internet but thats a risk i take bc as you said no os is best and its just simpler to do it that way for me. There really is no difference abt the cli between windows and linux tho. As you claim too you dont need to the terminal at all. But lets see how we see the ip for instance, on both linux and windows you type ipconfig into the terminal. Idk if linux users think they are smart or what, maybe linux is superior hence they use it but let me tell you, linux isnt good yet imo, its only good bc windows is bad. If you dont have issues with windows you are lucky id say. So in the end you are on the right track abt 99% of things i dont get why you have hard feelings abt cli. How will you findout your ip address for instance?
In Windows I can view the IP address through Network Settings. I haven’t used CMD except for a workaround to bring back the old File menu, and I’m not sure what I read. On Windows I also don’t need my IP address. As mentioned in that discussion, this can be handled in Windows without using the command line. Connecting another PC in a home network feels like a simple task, not a technical job. I believe there’s a lot of overconfidence in the Linux community. People think they know how to copy commands and sometimes it works, but they act like they’re experts. They often overlook their own limitations and are more likely to damage their system. This isn’t targeting you—it’s for many users. If you think this thread applies to Linux without using CLI, I’m listening.
I studied on a Robotron KC 87 and later on an MS DOS PC. At home I pursued a Commodore 64. My CLI experience was limited—mostly trial-and-error with hex codes on the C64, and some assembly coding without much progress. I once helped a friend troubleshoot a laptop, which led me to explore MS DOS from a diskette. Eventually, I found a hidden switch that powered up Windows 3.11. Even without internet or modern tools, I managed to figure things out by intuition. Over the years, technology shifted: from W95 with strict 640KB limits to W11 with internet and XP. Linux gained popularity, now making up just 3% of desktop users, while most rely on GUI-based systems. I suspect only a tiny fraction—perhaps 1%—actually use CLI today, either because they avoid it or rely on AI assistance. I don’t claim to be right, but I wonder why so few people still master CLI after all these years. My approach is cautious: I only use CLI when necessary, like fixing bugs or cleaning bloat. In Windows, I rarely need it, and in Linux, help resources are abundant online. Without internet, even basic tasks would be impossible.