Ya, I found the author's justifications for decisions pretty unconvincing.
Of course VSCode keybindings aren't great, but there are excellent Vim keybindings for VSCode, and that's the only thing about Vim that really matters. There are even experimental Helix keybindings for VSCode, and that's the only thing about Helix that really matters. Everything else is just commodified IDE functionality, and VSCode does that best.
And sure, Microsoft is not the kind of company I want to be entirely reliant on. But VSCode is MIT-licensed. There are already tons of forks for various purposes. Switching from VSCode to Helix for this reason is sort of like switching from Chrome to Lynx because you don't like Google. Why not just use Chromium, or Brave? With the level of adoption and support for VSCode, you can bet on well-supported forks popping up the moment Microsoft does anything truly destructive with it.
I mean, if you just want to try out and learn Helix, that's great, but the usability and morality pretense is distracting.
Of course VSCode keybindings aren't great, but there are excellent Vim keybindings for VSCode, and that's the only thing about Vim that really matters. There are even experimental Helix keybindings for VSCode, and that's the only thing about Helix that really matters. Everything else is just commodified IDE functionality, and VSCode does that best.
And sure, Microsoft is not the kind of company I want to be entirely reliant on. But VSCode is MIT-licensed. There are already tons of forks for various purposes. Switching from VSCode to Helix for this reason is sort of like switching from Chrome to Lynx because you don't like Google. Why not just use Chromium, or Brave? With the level of adoption and support for VSCode, you can bet on well-supported forks popping up the moment Microsoft does anything truly destructive with it.
I mean, if you just want to try out and learn Helix, that's great, but the usability and morality pretense is distracting.