We were forced to do it just to make it work the way we wanted. It was necessary. Hell, even semi-regular routine of formatting [the hard-drive] and reinstalling Windows because it was getting slow; taught a lot of people the simple basics. All of that is lost today.
Factory reset -> input email & password -> sit back while everything reinstalls. What do you learn from that other then to make sure you had a backup of your data.
I had a draft UDMA/66 port on which I wanted my MASTER IDE (for performance), but Windows would not install on anything above UDMA/33. It would run fine once installed, however. The procedure was straight forward, but IDEs didn't announce its presence, instead there were manual MASTER/SLAVE jumpers on the drive themselves that would have to line up with the manually configured BIOS settings. Once Windows was installed, everything had to be physically pulled out, ports and cables changed, jumpers and BIOS checked or configured, enabling UDMA/66 (and thus disabling the 2nd IDE port, but not 3 and 4) and you could start using the OS.
And Windows installation would BSOD with the network card in, so that would have to be added later but before downloading the necessary WaReZ.
I also got into Linux at the very end of the 2.4 line, and vividly recall how everything changed to be more user-friendly with the 2.6 series of kernels.
If an individual wants to learn, they only need to pop the hood, look inside the machine, and check out tutorials and videos on youtube. Plenty of people grew up with computers and never learned a thing about how they worked, they'd just have someone else who knew about them fix their problems.
We weren't forced to learn about them or had to, we chose to. That choice applies today as much as it did 25 years ago when I had to have my dad fix my computer for me. I just happened to want to learn how he did it and how to do it myself.
But this is most likely my own familiarity bias?
That's my personal one. I'm sure it'll be different for everyone else.
I doubt most people, with the exception of builders of custom rigs, even know that a driver is a thing.
My son, recently of age, has no fucking idea about anything beneath the GUI. OTOH, my somewhat older stepson is a games and recently "full stack" -- which has something to do with tis newfangled Web thingy, I think -- programmer. (OTGH, fuck knows what he knows of anything beneath Unity and React...)
___
[1]: That is, press a number and then [Enter]. This, I later (after some rudimentary hints on DOS from a classmate) found out, called the batch files 1.BAT, 2.BAT, etc, which in turn set up whatever needed to be set up and then started the respective application.
In my experience, students understood computers a LOT better after being told that their term paper is not recoverable from their busted HDD, and that they should be saving their work on the network drive in future.
These are terrible things to have to spend time on. This comment section reads like someone missing having to set dip switches on sound cards so they don't conflict with your printer.
Oh for sure, this gave me nostalgia of cracking pirated SimCity ISOs I had downloaded on Kazaa or Limewire or whatever it was that week.
Cracking ISOs with key breakers, patching DLL files, etc... all taught me a lot about how programs worked at a really young age.