1799
Comment on a YT video about Windows on ARM
(lemmy.world)
Installing OS, 10 years ago:
Windows: click a couple of buttons enter username and password
Linux: Terminal hacking, downloading shell scripts from github
Installing OS today:
Linux: click a couple of buttons, enter username and password
Windows: Terminal hacking, downloading shell scripts from github.
Link to video: https://m.youtube.com/watch?v=qKRmYW1D0S0
I think the biggest shift in the last 20 years is troubleshooting in Linux and windows.
20 years ago and I had to troubleshoot issues and Linux. It genuinely required a good bit of computer knowledge to get it done. Sometimes hours of work to figure out how to get a webcam to work Or how to fix grub?
Windows back then used to be so easy. And there was usually something that would do a quick fix.
However, now and I run across a windows issue. It's a nightmare. I can put hours of work into trying to fix a driver issue or an issue with updates and get nowhere. Then go to reinstall the operating system and have to spend more hours just to get it installed.
Now in Linux, not only do I rarely have issues but also fixing those issues are pretty straightforward. And if I can't fix it a reinstall takes minutes and I'm back up and running in no time.
Windows tries to obfuscate any useful information while Linux tries to give logs and man entries to walk the user through what went wrong.
As a part-time sysadmin at my small company. We use Altium and Solidworks, so we need windows.
I have 10x more windows problems than Linux problems like a bug for around 5 or so people where a windows update would disable the microphone, but every single microphone menu and setting would say it is enabled and working properly. You HAD to use their troubleshooter (which they are now phasing out, wtf) in order for it to be auto fixed. So soon it will probably be replaced by something else that won't fix the issue.
0 information online about it, 501 different way to fix audio issues, none of which work.
Nowadays the only problems that I have with Linux are slight bugs or user errors, honestly.
When the BSOD code has nothing to do with your actual problem
Well OBVIOUSLY you need to set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session\Windows\Microsoft\Win10\MSWindows\CockNBalls\BSODWord to 0 then restart your computer.
NOOOOOO please you're reawakening 20+ years of accumulated Windows trauma π π π
That was so confusing and stressful I don't know how I --or anyone-- survived the mental strain of regularly troubleshooting Windows
You forgot that you also need to create a new 32bit word entry with the value of the amount of system RAM in gigabytes times 2 divided by the square root of your age times 10.
Otherwise BSODWord won't be picked up.
Edit: also you need to redo that every time your system updates because Windows update will reset all those values
I went through that phase too! The tweak times are so much fun and breaking things is a good way to learn.
Now I am in a sane defaults mode. Where I just want everything to work well. Pop on so far has been rock solid. I actually have been trying to not touch the terminal to see how that feels as a user. In been 4 months and so far it hasn't been a problem.
I wanted to dual boot Windows 10 for a few games after I switched off. I can't get the damn drivers for my hard drives to work. I just gave up on Windows entirely.
The easiest solution was just "eh, I probably don't need that anyways"
Honestly was my solution for years I never use my webcam π
Nowadays I just roll my Linux installation back to before the updates using the BTRFS integration with the package manager. It works great and I'm never at a point where I can't use my computer because updates broke it. Heck, even if I bork it myself it's no biggie.
Yeah, same for me with NixOS
THANK YOU. I'm sick of this rhetoric about Linux being hard and user-unfriendly because of the command-line.
Windows is such a pain to use for a while now. You need a ton of post install scripts and hacks to make it even remotely usable and when something goes wrong good luck figuring out what. The event viewer is usually just a bunch of vague COM errors with an ID. Then when you look up that ID it's barely more useful than "something went wrong".