this post was submitted on 31 Aug 2023
376 points (96.5% liked)
Open Source
31359 readers
65 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
More context please. There are a ton of things that "just work" on Linux, just like Windows. I have spent hours troubleshooting and configuring things on Windows as well.
With either OS, time spent configuring and installing things is heavily dependent on the experience of the user and their ability to interpret logs and error messages. With most OS's, configuration and troubleshooting is just a matter of "knowing where to look" combined with understanding how the OS itself works.
Server services are much easier to configure on Linux, IMHO. Additionally, I find configuration to be much more flexible and (generally) more intuitive than Windows but that is my opinion. However, I have worked with both Linux and Windows since they were created, so I have a good number of years of experience.
My point is that it really depends on what you are wanting to do.
(Rant: Deep troubleshooting in Windows has always sucked and the methods to do so have changed a thousand times over the years. It's a royal pain to keep up, TBH. Very rarely have I needed "reinstall Linux" because something was broken beyond fixing.)
The guy before isn't exactly wrong.
Many things that "just work" on Linux are things you just don't do on Windows. E.g. swapping the DE or theming/customizing the whole thing usually works great out of the box. But on Windows you just don't do that.
On the other hand, getting e.g. legacy Nvidia drivers working correctly and setup so that it automatically switches between the power-consuming dGPU and the power-saving iGPU is a major pain in the rear. On Windows that just works. Mostly Nvidias fault, but to the user who has to deal with the situation it doesn't matter who is at fault.
And in general, if you come from Windows with a lot of Windows experience and then have to dive into Linux, you mainly notice the things that don't just work on Linux.
Also, fixing problems in Windows might take you through the registry or arcane wizards. But you hardly ever get into CLI and never into config files. So if you swap over to Linux, where almost any help you find online will go straight into CLI and config files (even if a GUI solution would be available), that can be pretty jarring.
I've been using Linux professionally for ~15 years and privately for ~5. But I still remeber getting into it very vivdly.
Very good points. I remember the drama of trying to get simple things like USB, Bluetooth and even WiFi working on Linux quite a few years ago. However, even though those could be problematic, I did learn a ton about how drivers interacted with various chipsets. That, in turn, led me down the path of how to apply specific patches and build my own kernel modules. It was absolutely a double edged sword.
It really is a shame that most GPU vendors haven't spent more time developing better drivers for Linux, but in some ways, I feel their pain. (I am leaving out the open vs closed source debate on that.) Windows does provide consistency, through all of its shortcomings. Linux can be very .. eh.. interesting between different distros, for sure.
But yeah, I didn't rush to downvote the above commenter as they were speaking from their own perspective and experience. No shame in that.
Uh, Wifi drivers in the 2000s on Linux... That was painful. I remember one specific Wifi USB stick, where the Linux driver just came as source code. I mean, good for them for making an open source driver, but back then I was just a teenager with very little coding experience, and they had no guide on how to compile it at all. Also it was written for an older version of gcc than what I had, and gcc threw a ton of errors because that. So I had to go through the whole driver source and fix all these compiler errors, even though I had no C++ experience at all. Just to get a dumb Wifi stick to work.
In Windows, back than, it was just "plonk it in, double click the driver on the CD and be done". I don't miss those days.