Correct. If you've got no background in vim, it might be a good thing Helix has broken "backwards compatibility" in order to have more cohesive key-bindings.

But then you'd not be comfortable with the hundreds if not thousands of other packages out there that use vim bindings.

I think folks might be over-estimating the difference between the Helix and vim. IME, adding "ge" to Vimium[0] was good enough to have any conflicting muscle-memory. I don't think it's much more than lots of folks are already configuring on their own in their vimrc (e.g. installing plugins like vim-unimpaired).

I'm not sure that I buy the purity argument -- almost all "vim modes" in other software are interpretations of the vim key-bindings and not an embeded vim/neovim engine. As a result, they all have their own caveats and folks using vim get used to functionality that exists exclusively in their vimrc.

[0]: https://chrome.google.com/webstore/detail/vimium/dbepggeogba...

Yes my problem with helix is when the keystrokes that are muscle memory in Vim don't have any actions in helix this makes it problematic to move to helix

over moving to neovim for example neovim retains most if not all the vi keystrokes not just out of respect to the vi authors