I'm an old coot. when I was 19 I worked on the testing floor among PDP-11s and vt-100 terminals.
There was SCO unix running on one box and it seemed necessary then for it to be verbose about all it's doings upon startup and shutdown. You know, screens of daemons and services coming to life and being killed . The file system ran out of ram so it could service all those vt-100 terminals with a measure of speed, but oh don't you loose power or you'll have lost and scrambled inodes with only an fsck to fix it. This required a fighter pilot.
OK that was 1979 ish, so it was ok.
Here I am in 2020 and linux still likes to show you it's daemons upon start and stop which just for starters will put off just about any normal person. And the when it looses juice it still corrupts it's file system and it still takes a fighter pilot to go sudo su fsck /dev/sdc0 put in the password, be admonished about inodes, know how to respond etc.
Windows doesn't like to be kicked either but it by and large can repair ntfs by itself.
I know a guy who is one of these linux guys to be a linux guy. - I agree with the Charlie Brown great punpkin analogy.
Computers and phones are like cars or ratchet wrenches. We expect to just use em without thinking or fanfare. Linux guys, well I just don't know.
It's still that "scary" unix.