I wholeheartedly agree that there is more to Vim than jkhiI$&0... but berating such a fantastic product is very counter productive.
Instead, think of ways (or contribute ways) to improve the VIM plugins to Code Mirror. Even suggesting which other parts of VIM you find so useful would be of more use than berating them for using VIM plugins instead of VIM itself.
Ignoring OP's harshing, it does seem hopeless. There's little incentive. Probably the easiest way is to compile vim direct to javascript (or java), and ignore/hack the OS integration. Unfortunately, improving the plugin seems to have fundamental limits (see the js for the actual bindings http://codemirror.net/keymap/vim.js - there's a few more than I'd expected):
> Because CodeMirror's internal API is quite different from Vim, they are only a loose approximation of actual vim bindings, though.http://codemirror.net/demo/vim.html
From a theoretical point of view - all text editors offer nearly the same feature set, so all features should be available through a different set of keybindings.
In reality, of course, this can be difficult if the editor doesn't offer reasonable support for accessing all of the keybindings through the API.
Still, CodeMirror does seem to offer better support than most.
Comments
I wholeheartedly agree that there is more to Vim than jkhiI$&0... but berating such a fantastic product is very counter productive.
Instead, think of ways (or contribute ways) to improve the VIM plugins to Code Mirror. Even suggesting which other parts of VIM you find so useful would be of more use than berating them for using VIM plugins instead of VIM itself.
Ignoring OP's harshing, it does seem hopeless. There's little incentive. Probably the easiest way is to compile vim direct to javascript (or java), and ignore/hack the OS integration. Unfortunately, improving the plugin seems to have fundamental limits (see the js for the actual bindings http://codemirror.net/keymap/vim.js - there's a few more than I'd expected):
> Because CodeMirror's internal API is quite different from Vim, they are only a loose approximation of actual vim bindings, though. http://codemirror.net/demo/vim.html
From a theoretical point of view - all text editors offer nearly the same feature set, so all features should be available through a different set of keybindings.
In reality, of course, this can be difficult if the editor doesn't offer reasonable support for accessing all of the keybindings through the API.
Still, CodeMirror does seem to offer better support than most.