25 ms·
How does Lapce compare to Helix, also written in Rust, is modal like Vim, has a built in LSP with sane defaults, etc? https://github.com/helix-editor/helix htt
by cercatrova 4y ago
How does Lapce compare to Helix, also written in Rust, is modal like Vim, has a built in LSP with sane defaults, etc?
https://github.com/helix-editor/helix https://github.com/helix-editor/helix
- manaskarekar 4y ago> Helix's editing model is strongly inspired from vim and kakoune, and a notable difference from vim (and the most striking similarity to kakoune) is that Helix follows the selection → action model. This means that the whatever you are going to act on (a word, a paragraph, a line, etc) is selected first and the action itself (delete, change, yank, etc) comes second. A cursor is simply a single width selection. I believe Lapce follows the original vim model. For further reading about the object-verb model: https://kakoune.org/why-kakoune/why-kakoune.html https://kakoune.org/why-kakoune/why-kakoune.html
- Xevi 4y agoI don't have any experience with vim or other alternatives, but after reading that article or seems like kakoune is way better in practice. I wonder why Lapce didn't go with "object -> verb".
- manaskarekar 4y agoI think many would agree that object-verb is the better way, but the vim way is old and more established. I would imagine the sheer number of users would be far more for vim’s model. That said, it’s a mode that could be introduced in the future as kak-mode I suppose.
- iza 4y agoLapce is graphical and seems to be aiming for a vscode-like experience, while Helix is a terminal-based editor. They're not really competing in the same space imo.