> Compare this to Vim where, if it's the first time you're opening it, you are forced to kill the process because
Because you can't readI'm serious. Open a blank file by typing `vim` into the terminal. Don't press anything, just look at the screen.
I'm sorry, but reading docs, or just reading, shouldn't be considered a significant barrier to entry.
How long have you been developing code for others to use?
Rule number one is that users don't read documentation.
> Because you can't read
A lot of people can't, that is why vscode is so popular
You're not going to be making successful customer-facing software with that attitude.
> Compare this to Vim where, if it's the first time you're opening it,
If you open vim with a file, like you do with all file editors, there's no such examples. It's also at the bottom of auth/credit/contribution fluff in your example, which people would be expected to ignore.
> Because you can't read
I'm not arguing for more hand holding here, but saying the poster can't read is ironic. Reading is one part, comprehending is the other.