Getting them to stop and read what’s in front of them is one of the hardest things to do.

Personal opinion, that's not because the errors aren't useful, it's because people refuse to fucking read signs. It's not about Windows/Linux, it's that most people can't be arsed to pay attention to much of anything.

Source: Worked as a pool attendant with a gate. Gate had a sign with rules for the pool and instructions on how to open the gate latch. The number of people confused by the rules and the gate because they failed to look at the sign right in front of them was consistently higher than the number of people who stopped for two seconds to read the sign.

Having learned how to use computers via MS-DOS, then growing to mostly use Windows machines, and then moving to daily-drive Linux in the past handful of years, I think the problem is more about context. If I see an error message, it's not that I don't read them. ‌Rather, if I lack the context to understand what it is trying to tell me—and more importantly, what I‌ can do to resolve the problem I'm having, I'm out of luck and I'd have to ignore it.

It was when I switched to using Linux that I've picked up the habit of searching the error message online, and then browsing the various pages (mostly Stackoverflow, sometimes Arch Linux wiki pages) which might or might not lead me to the context behind the error message. If I get lucky, I could find a clue to resolving my problem on top of understanding what the error message is about. Other times, I end up being even more confused and give up.

And then there's the monstrosity that is the logs. I'm pretty much illiterate when it comes to them, and reading them might as well be reading arcane records of eldritch daemons keeping my machine working (in a way, they indeed are). Copy-pasting some snippets from them into an online search is a crapshoot. I may find something that fits my context, but a lot of times, it's for a different problem. It might not even be for my OS/distro/package/version.