this post was submitted on 09 Nov 2023
1 points (100.0% liked)
Framework
76 readers
1 users here now
Discussion around the Framework mission of building products that last longer by making them upgradeable, customizable, and repairable. Consumer electronics can be better for you and for the environment.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Tbf, DOS and computers back then were simpler than today, making it easier to troubleshoot comparatively.
Win 3.1 added a bit more complexity on top of that. Basically we built more complex structures on top of older simpler ones to make it more and more user friendly. The more user friendly, the more complex the underlying tech to make it user friendly (harder for techie people to troubleshoot since there is so much more going on).
That's why SBCs like the RPi are gaining traction. It's like going back a few steps so people have an easier time learning some of the underlying basics of computing.
DOS troubleshooting sucked. I still have nitemares about battling QEMM 386 to free up a few more KB to get a game running.
For me troubleshooting wasn't the issue with memory. Especially once I know the difference between extending expanded etc etc. Of course I forgot them all now lol. Manga shoes typically revolve around irqs and other resources. However once I got a mental map of all my devices and what resources they were using I can typically resolve conflicts unless I have two devices that conflicts no matter what you change. Then it's not really a troubleshooting issue it's more of a resource issue and I know it.
I remember making a multichoice auto exact file that lets me customize how to set up memory management for specific set of games
I had not really thought about that, but you're right. The example holds throughout my experience. I use Linux daily nowdays, but I used to be a Windows power user.
I can confidently claim Linux is easier to use than Windows. And I mean it seriously, I'm not trying to be controversial. It's nowhere near as complex as Windows and structurally many things are easier, it has less abstraction, so, whereas it might require a bit of a learning curve in some places, when you've done it, you're done because you fundamentally already know how it works. Also, while the GUIs are now slowly starting to get better and cover more of the experience, for the most part, Linux distros don't make many attempts to hide the underlying workings to the end user, and documentation is provided for anything, so if you're curious to know how anything works, you can just read up on it and get a decent grasp.
Windows tries to hide how it works from the user, and that is what causes it to be so hard to debug. When something breaks on Linux, after a few years of experience and a "clinical eye", I can pretty much always accurately guess where in the stack the disruption has happened. Maybe it takes 2 or 3 takes to get it right, but at the end of the day, I have a honest grasp of how a modern Linux system is put together and I can get my hands dirty. On Windows it's… not that simple. I feel like I am talking multiple shots in the dark and just guessing semi randomly hoping that the next attempt will fix it instead of leaving my system in an even more broken state. Because the admin tools are there - regedit, powershell, event log, performance monitor, whatever you want - but it feels like doing surgery "blindfolded" in a way. Trusting what you read on some forum and hoping this long ass powershell command will do it.