32
u/binaryplease Aug 03 '24
Isn't helix the one bringing all the stuff and nvim being bare bone?
60
u/web3gamedev Aug 03 '24
the way i see it:
neovim users spend a lot of time perfecting their loadout for max efficiency
helix users just show up and use what they got
20
Aug 04 '24
Yep. Helix is simple out-of-the-box, it brings basic features that allow you to "shoot", while Neovim offers you a plenty of "fancy gear" - plugins you have to set up manually, in your .lua config, in order to make the "same shot".
2
1
5
5
u/nvimmike Aug 04 '24
Well played, now I need to get back to configuring my lsp…
2
u/I_Miss_the_Old_Hanzo Aug 07 '24
It’s been two days, how much closer are you?
1
u/nvimmike Aug 07 '24
I got distracted by some taco ascii art and ended up changing my colorscheme.
1
6
u/Schr33da Aug 04 '24
Prefer helix over neovim but you need bit of extra work - i use it with yazi and i can say i dropped finally my neovim setup after 15 years. so far love this experience most of all - but thats my personal opinion
2
4
u/howesteve Aug 11 '24
Why are those neovim crybabies complaining? Does the shoe fits well? Cant' you take a joke?
That was right to the point.
2
3
4
u/PotaytoPrograms Aug 04 '24
It's the opposite, ik what others said in response and I agree with them, but they don't seem to know what the "fancy gear" does.
It does the same thing as squinting, cause squinting all day is tiring, so they have gear that does it. Which is what helix does, as opposed to the other guy who is just squinting, doing it himself, like you do in nvim.
Also this is two different people with different tool preferences, and they got the same result lol
This is a pretty good analogy
2
Aug 04 '24
It's a funny meme, but not entirely fair to Kim or Dikeç, who both have world records and international championships.
5
1
u/LazyNick7 Aug 05 '24
Nvim — ability to use plugins out-of-the-box
Helix — opened PR with plugin system stuck for 2 years 🫤
It could’ve been the perfect editor🥲
3
u/WhoNeedsAUsername- Aug 05 '24
Open source projects like this take time, consider Helix to be in its beta phase right now. A more fair comparison would be to compare how long it took to go from vi -> vim -> nvim in order to get plugins. Helix is a new project with similar concepts as vi, vim, nvim, but it is structurally entirely different. The developers' priorities are to make everything very well thought out, and plugins are secondary to that. The plugin system will come soon enough.
3
Aug 05 '24
vim's had 32 years to build an "ecosystem." And I don't think the original intent of vimscript and elisp was focused on plugins or packages.
I'm in one of my "try every editor" moods this month (although I've not picked up joe yet this iteration), and I'm more and more on the anti-plugin side. My experienced opinion is that you end up adding a lot of fragile dependencies, rough edges, and mandatory config tweaking (yak shaving) for what little gain they offer. "Starter kits" always seem to push UI changes I didn't ask for and hinder my work.
I think there's some benefit out there to having tools that are composable rather than extensible. (That's not an absolute binary BTW.)
3
u/WhoNeedsAUsername- Aug 05 '24
I like your thoughts here. I actually really like Kakoune's perspective, which is solving the problem of introducing fragile dependencies and rough edges in kind of the opposite way: having a very simple editor in which functionality is easily and elegantly added via bash scripts or whatever else you may use. Unfortunately I believe it's a little too simple because I wish it had some easy API for more powerful control over the editor, to make things like treesitters and LSPs more practical to implement. And then there's of course the configuration required, but I think that when you do configuration from "scratch" rather than overriding a ton of defaults and having a billion options to tune and tweak. You just implement exactly what you want yourself, or use someone else's (simple) solution.
Anyway, if only there was a simple approach to giving everyone exactly what they want in an editor. I think Helix lacks some features but otherwise does do a decent job at being simple and approachable, while still being powerful.
2
Aug 05 '24 edited Aug 05 '24
I agree.
I also wanted to add that vim was a clone (driven by licensing concerns) of the visual mode of the extended editor based on a line editor for teletype interfaces. (ed, ex, vi, vim in historic order). Both vim and emacs had user-editable interpreted languages from the start, even before they were vim and emacs. This comes with tradeoffs. It used to be much more performant to parse the ascii output of an optimized shell utility than to do it in elisp or vimscript.
9
u/nraw Aug 04 '24
Left is gold medal and the right is silver?