> the more intuitive the tools are the better it is.
"Intuitive" is a pretty vague virtue, and I'm not sure that VS has it.
If we're talking about discoverability of a feature, I guess you could say a tool that exposes most of its options and features through a wide swath of icons and giant tree of menus leading to various dialog boxes of doom has something of an edge in that one can walk down all the paths until a desired option is found (or not found), and each point is something like a flag that says "Hey, feature here!" Then again, it's hard to tell how relevant or irrelevant it is to what your needs are, and I can similarly walk/search through documentation for a given text editor until I accomplish the same thing.
> What if somebody just wants to get things working fast and does not want to learn how to make the cursor move up in vim?
There are some pretty nice text editors out there that have keybindings considerably more intuitive than vim. Even gvim has two intuitive ways to move the cursor (arrow keys + mouse).
There's the question of which keybindings are most rewarding to the user who puts time in, too. The longer you're going to spend in a tool, the more important this is relative to how easily discoverable features are.
> it's becoming more and more about the result and not about the process.
Becoming?
> hours spent on figuring out why something is not working when it should is becoming rather an avoidable annoyance
Certainly not my experience with Visual Studio over the last year.