this post was submitted on 07 Mar 2024
1414 points (93.0% liked)
linuxmemes
21280 readers
1101 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows.
- No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
I am currently dual booting and trying to get feature parity in my Linux install as a reletave newbie.
So far the largest hurdle I've been able to solve was getting my RAID array recognized. That sent me down a rabbit hole.
To get it working in Linux I needed to:
To get it working in Windows I needed to:
You'd normally use a software raid implementation these days, and Linux has a number of those. But yeah, dual booting can expose some quirks and filesystems and disk setup in general is one of the most prominent.
This. How an advanced use case is accomplished is not a point against a system's usability.
The point I was trying to make is that if you ever want to do something that is not covered with an out of the box install, it's typically far harder to do in Linux than in Windows (although my ~15 years as a windows sysadmin probably bias my opinion)
Windows is turning into a telemetry nightmare because about 10 years ago Microsoft figured out that they could sell ad space and monetize user data, so I'm trying to get off the platform before my LTSC install hits EOL. But I have to admit it's a hard path.
Now do a raid like it's typical for Linux and get it to work on Windows.
Oof, hoops you have to jump through to get two disks in a mirror on windows still haunt my dreams sometimes
So basically: it's not any harder in linux, but you have more than a decade of muscle memory in windows, so it's harder for you.
That's like saying "Japanese is a less efficient language than English, all of the words are different, and when I want to say a word, I have to learn it first, but in English I just know the words! English is so much better! (My 30 years speaking english probably bias my opinion)"
Things are certainly different, but its hard to compare which is "harder" for the advanced use cases.
There's no shame in having long term experience with one platform and having that shape your expectation about how a solution should look.
But in your example raid controller driver was covered in an out of the box install in windows. If it wasn't you'll still need to do pretty much the same. Also there was a couple of weird steps in your linux list like switching DE to run a couple of CLI commands and disabling AHCI for some reason.
Congrats on taking the plunge. I suspect there are others like you.
I'm actually kind of envious. The joy and frustration and joy again of exploring something new was something I relished in my early Linux years. Back then you had to use a text editor to configure your video card before even getting started, so it was kind of insane haha. But totally worth it later, as all of those skills translated.
For advanced, power user stuff, I find Linux to be much friendlier and faster. Just being able to do everything in a Terminal instead of having to mess around with a mix of inconsistent GUI menus in the two different control panels, gpedit, regedit (which is an entire headache by itself), a mix of cmd and Powershell (and whatever Windows Terminal is) is just so much less of a headache.
Also I find things easier to script in Linux compared to Windows.
Not to mention the mess that is Windows Update, which doesn't even upgrade third party software, and takes a long time to actually do the updates. Package management is a godsend. Windows has chocolatey and winget, but those are poor substitutes.
And I say all of this as someone who is technically proficient in both.
This is kind of the same situation I'm in, but I'm not quite as tech savvy and I'm more resistant to learning linux even though I'll still probably want to migrate over at some point.
What I don't really understand is, or, what I understand, but I suppose I find mildly amusing, or confusing, is how many criticisms I've seen of windows that kind of just don't apply to LTSC as much, if at all? It's kind of to the point where I wonder why anyone would really use any other version.