To be fair, usually a new user's first encounter with vim is it being the default editor when trying to edit a text file. If you open a specific file with it, you won't see the intro.
But if I type :q! it just appears in the body of the text!!
The one the that gets me is when I accidentally open a command window when trying to exit and I have to :q out of that first.
People who say this don't know google exists
Google literally didn't exist when I first was thrust into vim (well, vi) a large number of years ago ;) Pretty sure I eventually gave up and closed the terminal window - dialed directly into the university's unix server. Can't remember which version of unix it was, though.
It was probably the default editor for tin, the usenet client I was using. At least pine used pico as its editor which was a bit more friendly.
I'm outing myself here, but a computer programming class in college has forcibly thrust all two dozen of us, none of us ever touched a Linux machine in our lives prior to that point, into using
vi.And all using the command-line from boot-up.
Cue hilarity as we spent a good hour or so trying to fumble our way into creating our first C program. Made some friends that day though, so I guess that was the intent? Camaraderie through shared suffering?
Or it's a meme about the cryptic UX and not an actual question. I mean how many non-gaming software require a tutorial as introduction.
In Neovim, when you press Ctrl+C it switches to normal mode and give you this:
but there's the switching between input modes
