this post was submitted on 07 Mar 2024
1415 points (93.0% liked)
linuxmemes
21605 readers
668 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
sudoin 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 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean, you don't HAVE to do any of that stuff in Windows, it's just helps a bit.
I'm sure there are plenty of windows horror stories. But almost every Windows computer I've had in the last decade, both custom and OEM, has worked pretty well out of the box. And almost every Ubuntu computer I've had over the last decade has had problems that weren't trivial to fix.
I like Linux, but when people compare these problems like they're the same just are missing the point.
Yep exactly this. The user friendliness and likeliness it just works is much higher for Windows.
If it doesn't work for Linux I've found it also will generally take much longer to figure out and fix.
Sure because
Error Code 0x8007057tells you immediately how to solve the problem.Linux error messages like
error: kex_exchange_identification: client sent invalid protocol identifier "GET /robots.txt HTTP/1.1"are completely arcane tough.I support both systems. And Linux support is so much easier. Mostly in runs out of the box. If it runs I continues to do so and If you have an error you get a specific message like above.
With such a message you either:
With Windows: No systems runs out of the box, I always have to install additional software (7zip, sane browser, ...) and also for anybody remotely privacy concerned have to adjust many settings (for which tools exist thankfully)
If an error occurs under Windows and I get a code like above:
I agree those kinds of arcane windows errors suck worse than they do in Linux. But I get those errors so rarely on either system.
In Windows, I'll have something happen like my windows won't remember their last position when I unlock.
In Ubuntu I'll have to restart my Bluetooth service every week or so. Or sometimes the update-software modal will not take focus or accept mouse/keyboard input until I reboot. Most recently I had an app from the official app store fill up my entire partition because it spammed syslog, which broke my credentials cache, and I couldn't even log in until I made a temporary sudo user and emptied syslog.
None of these are super difficult, but they also don't provide error messages.
My experience is summed up as: -If it is broken in Linux, I will have to fix it, but with knowledge the errors are diagnosable and reparable -If it is broken in Windows, it has a decent chance that it will fix itself. However once it fails to fix itself, then it's maddening to figure out how to repair it leading to the "screw it, just reinstall"
So if neither one breaks, congratulations, they both seem pretty solid.
If a fairly common breakage occurs, Windows looks weird but it fixes itself, Linux meanwhile bleats what is an arcane error to a non-tech person, maybe refusing to boot.
If a really stubborn breakage occurs, advantage back to Linux as at least a skilled person has a chance of repairing it.
7zip built in now, and edge is decent
The true test is, would you install it for your mom. Have fun figuring out her public library and ereader shit on Linux.
I've installed it for my mom. She mostly just checks mail, writes some documents and browses the web. She said she didn't notice a difference, everything worked as it should.
Sure, but then I upgraded my working out of the box Windows 8 machine to Windows 10 and it became unusable because it has a hard drive, not an SSD. Select between running an unsupported system and being able to use your computer without it stuttering every 2 seconds...
I do admit I don't really trust the windows upgrade process. Not for any specific reason, just vibes.
I haven't used an HDD in a long time, so idk the current state of affairs, but when win10 first came out, HDDs were fine. That's a bummer though, and win10 is more expensive both in the cost of the OS itself and in the hardware you need to buy for it. You can run Linux on a potato. But that's not really the kind of issue that this post is talking about, afaict.
Now, it's unusable with a HDD. LTSC is barely usable with a HDD. Win11 on a HDD, no way. Have tried it, it boots for like an eternity.
exactly