I'm teaching Git in University.

For all those who think that Git is easy, it's not.

It takes a student about 20-30 hours to really understand all usual Git commands. I'm not talking about something bizarre like ls-remote, but really understand merge, rebase, bisect. Not just syntax, but all the consequences. For instance, why rebasing something already pushed to public often leads to false merge conflicts, how does stash really work, etc.

I don't think Git is easy at all.

But 20 hours seems a worthwhile investment to me for something they will likely use for at least the next decade of any serious work with software? I'm assuming that this doesn't mean literally 20 hours of instruction.

> But 20 hours seems a worthwhile investment to me for something they will likely use for at least the next decade

Yet most people just want to use VSCode and don't want to invest 20+ hours learning emacs or vim

Interestingly, the features of Emacs, Vim and VSCode are largely orthogonal (on top of any basic text editor). Further, a lot of people advocate using CLI instead of most VSCode features. Waiting for the holy grail, you can still learn from each:

* Vim key bindings for text edits

* CLI commands for Git

* Emacs modes such as Magit and org-mode

* VSCode for tight Typescript integration, nice block structure visualisation etc.

I hope some editor will combine this all. (I think Emacs will be best placed to achieve this with its extension ecosystem that already includes Magit, org-mode, evil-mode etc.)

VS Code already has extensions for all that.

VS Code doesn't have anything comparable to Org mode. The "VS Code Org Mode" extension[1] has maybe 1% or 2% of the features of Org mode for Emacs. Go read Org mode's manual[2] from start to finish (134,062 words) and then direct us to an extension for VS Code that has comparable features (e.g., plain text spreadsheets).

[1] https://github.com/vscode-org-mode/vscode-org-mode

[2] https://orgmode.org/org.html