Hacker News Reader

Comment by bad_user | Hacker News Reader

When comparing VS Code with Atom, vim, Emacs, others, an underappreciated fact is that extensions just work, and are very easy to install and configure, which has much to do with its model. Atom was unusable for me, because, as you installed extensions, something always broke.

This is also similar to the old Firefox vs Chrome. The former was great for power users, but it crashed a lot and Firefox installs of regular people were riddled with insecure extensions that broke the browser and that couldn't even be un-installed.

VS Code does have flaws, but having limited extensions is not one of them, IMO.

View on HN

They don't "just work". There are many many extensions that require external tools in the path etc. and some even go as far as to try to download such dependencies (and leave them on the system). Generally one should definitely read the extension documentation and there may be some manual steps needed (meaning that they don't just work).

It's true that the most popular extensions work fairly well though.

For the purposes of the general end user who really doesn't care whether extra dependencies are on the system, it does "just work." Indeed, they might even want such behavior, that plugins manage their own dependencies without any end user input.

> VS Code does have flaws, but having limited extensions is not one of them, IMO.

Exactly. Of course as somebody who writes extensions I'd sometimes like the possibility to change stuff at a "deeper" level - like having multi-line text decorations. But as a user I really prefer the model to the Emacs' one. Emacs (and I guess *vim) works best if the user writes all the code themselves.

> an underappreciated fact is that extensions just work, and are very easy to install and configure

This is partially because of cultural reasons. VS Code was originally a code editor made for web developers, by web developers. It follows directly in the footsteps of Atom. Web developers, for good or for bad, value the user experience of software working out of the box so they tend to bundle everything. Systems engineers, those of the C/Python camp tend to optimize for efficiency and prefers the user to manually setup out-of-band binaries.

Yep, I routinely get breaking changes with my neovim config, so I now keep both VSCode and neovim installed.

I've been using vim and neovim for over 15 years with many 10s of plugins and I can probably count on one or two hands when an update has caused problems.

Also use Arch for about as long.

It's so odd to me when someone says that updates break their vim or Arch frequently.

There are so many threads about it on /r/neovim that people have started to ask just which plugins actually work together cohesively without breaking [0], something that is not asked about for VSCode. Just go through their "Needs Help" flair and you'll see lots of issues [1]. For me, I also use tens of plugins but inevitably something breaks at least once every couple of weeks.

[0] https://old.reddit.com/r/neovim/comments/1c9ev8n/overwhelmed...

[1] https://old.reddit.com/r/neovim/search?sort=new&restrict_sr=...

just use lazyvim[1] and be done with it! some people takes care of the compatibility and they are probably more competent than you (i mean a newcomer who starts writing their nvim config)

[1] https://www.lazyvim.org/

Clearly you didn't read any of the threads as it is sometimes even lazyvim that causes these incompatibilities:

https://old.reddit.com/r/neovim/comments/1dgtyzw/lazynvim_do...

https://old.reddit.com/r/neovim/comments/1dp47gi/lazyvim_own...

One of those threads is about lazy.nvim, not lazyvim. The other is a question about what to do after accidentally installing lazyvim with the wrong shell on windows, not about plugin updates breaking things.

Lazyvim is powered by lazy.nvim, at some point it'll break. These are example posts, you can feel free to go through reddit for more examples but yes Neovim does routinely break more for me than VSCode ever does, which is basically never.

it never has been my experience! i have used lazyvim distro for the last year or so and run some :Lazy update for time to time and usually i just need to close neovim and restart and it will all be working well..

I think i had an issue when they moved to conform.nvim from the deprecated language server based method but that's maybe about it (I deleted the nvim cache and it was all good after)

Right?

I can count the number of times my vim and arch installs has broken without my intervention on no hands.

Your anecdote does not somehow counter dozens of others that clearly exist across the internet. Just because it works for you does not mean it works across the board.

100%

Arch just shipped a beta nvidia driver as release and heaps of people have found their system broken.

I keep hearing of bugs and breaking changes in neovim, with no sign of it affecting the upstream vim. I am a little frustrated that neovim could give people a bad impression of vim from a stability/compatibility standpoint. Unlike emacs and atom, where you can modify the editor fundamentally, vim is extended with sandboxed scripting language(s) (I assume the same is true with neovim as well), so there's no fundamental reason why an update should break your plugins. Conflicts can occur due to overlapping hooks, but VSCode has the same problem. To be clear, I'm not suggesting people switch their text editor.

Would love to hear from a more seasoned vim user if I'm missing some egregious stumbles in vim's updates that affected their workflow.

e.g the Lua API changes

Reply on news.ycombinator.com