The first issue I ran into was wanting to learn a replacement for one of the only vim-fu’s I know, which is like ci’ to replace what’s inside single quotes on the current line. After getting help from the (super nice!) community the answer was too complex and I moved back to vim.
I imagine these types of problems generalize since everyone has their own little muscle memories and workflows. It’s hard to replace such an entrenched tool. I’m always rooting for the new underdog though.
I'm kinda the opposite way, now. The normal mode in Helix feels great to me; you press space and get an annotated menu of keyboard shortcuts. Space + f drops you into a file search for the current directory. Space + w + h gives you a split, Space + w + w switches splits, and closing any one is a quick :q! away. To me it feels the closest I've seen a terminal editor get to that VS Code comfort of everything being at arm's reach. But it does take a bit of exploring to find the good parts; I also recommend micro to people that don't enjoy the modal editing lifestyle.
To replace inside single quotes, you can do `mi'c`. There's nothing to restrict it to the current line, but you will see the selection before you hit c. That's the big benefit of the noun-verb model that Helix uses.
I imagine these types of problems generalize since everyone has their own little muscle memories and workflows. It’s hard to replace such an entrenched tool. I’m always rooting for the new underdog though.