Windows doesn't "just work"
-
Have a different experience. Usually, Linux does not even boot, due to driver issues, in the first place. So, the first installation process usually easily takes 5 to 10 hours, straight. And this is only for common popular distributions, not to mention lesser known and lesser supported ones. (Talking about Linux GUI based installations, only.)
-
It's a WIMP system. They all work the same way. Worst case you have to click around a bit.
-
I think you were being biased.
- You heard the name of the software
- You search on Google, which takes you to their official website
- You click on the download button and download it
- Double click on the file and follow the on-screen guide to finished the installation
-
Curious what Bluetooth chip you have as this was my experience and the several devices and a couple different windows machines
-
It literally doesn't run dynamically linked executables without elf hacks
-
I almost never had Linux not boot after a fresh install, even with nVidia hardware. It happened a few times like 10 years ago and never again. What hardware are you running?
-
Happened to me all the time, when, for example, setting up very generic and common laptops for family & friends. It never worked out of the box. Every single time, I had to give special treatment. Research extra drivers, etc... Hard to do in some locations, when they do not have a second system to do all the work from.
-
Laptops have historically been a little iffy yeah. Personally I haven't had many issues except for Nvidia optimus, but since most of them are non standard and proprietary it used to be kind of a pain.
Now though it's much better, at least on newer hardware, even my newest laptop with hybrid graphics just worked out of the box. -
Tried it over many years. Last one was last year. Every time, the same problem. I even considered moving to Windows, but it would be tougher for me to administrate for me, as I'm used to headless Linux. It's just, whenever Linux tries to GUI, it fucks up everything colossaly.
-
I just don't see it. I run it on all my PCs with nvidia, amd, hybrid graphics, pretty much any combination (I have too many
). It works.
Even various friends of mine have tried it on their older setups, no problems there either.Unless you're using something like Debian or whatever with crazy old packages, everything works for the most part. Nvidia is still not great on Wayland but it at least works now.
I'm not saying your experience isn't valid, I'm not trying to gaslight you, but I'm not sure it's representative of the average experience nowadays.
-
Was windows dev for 10 years, I switched to Linux for work and I'm never going back : everything is simpler (may not be easier though) and makes sense whereas you constantly work against the system in windows. It's an opinion so widespread they even made a subsystem to use Linux tools on windows.
As a user windows installation is an utter nightmare, getting rid of the thousands stuff you don't want is horrible. And also you may not even be able to install it without special ssd drivers that you have to side load manually (for some pretty basic asus hardware)
Also don't get me started on the nearly mandatory microsoft account
-
If i have to suffer because I'm a dumb dumb, that's on me. I'm tired of suffering because other people are stupid.
-
I tend to disagree, I do have several devices running Linux and with all of them I had issues after install (standby not working, swap partition not recognized, sound only playing on half of the speakers, issues with monitor scaling etc...)
Im fine with it and like the journey, but there are still quirks.Probably Im in an in-between-world where I do have some tricky use-cases, but missing the full know-how to do it...
thing which makes it not normy-usable, are the documentations: for windows issues you can find DAU-conform guides to solve something. Mostly on "official" (with probably too many ads) pages.
For Linux it's usually a rabbit hole of official documentations (which dont show all the options), forums, reddit pages, where some guy tells another guy to add xyz to the config file....without telling which file and where in the file. Why is this command not listed in the documentation? What does that command actually do?
It has gotten much better, but there's still some way to go
-
yeah no i'm sorry but this just sounds completely fucking made up
-
Over the past 5 years, I've installed ubuntu about 30 times on different computers. Not once has an install on an SSD taken me more than an hour, with it typically taking me 30 minutes or less except for rare occasions where I've messed something up.
-
I think it highly depends on what kind of hardware you are attempting to install Linux on. You can make it work on almost anything, but the graphical installers are best used with hardware that was widely used when the distribution was released.
Also the older and more obscure distros may not have installers that pass secure boot checks, which is very frustrating if you don't know what is happening.
