[bbkane]

Wow, I love that so much stuff is coming to core!

Every once in a while for the last few years I overhaul my Neovim config and try to add all the new goodies (commenting, LSP, etc., that are table stakes for most IDEs) as plugins using the latest and greatest plugin manager.

That works for a while, but like clockwork, something breaks- a plugin updates incompatibly, Neovim updates incompatibly, an external binary the plugin relies on updates incompatibly...

At this point I'm stuck with a broken IDE and I don't have the energy to debug all the moving parts. I suffer for a month or something and then restart the cycle.

For my latest config, I decided to treat Neovim and "just a text editor" and made a much smaller config ( https://github.com/bbkane/dotfiles/tree/master/nvim-03-lazy ). It's been really nice having something that "just works" for text edits and using VSCode for heavier IDE tasks.

I WANT to use Neovim for more complex tasks, but I also want a simple config that "just works".

I'm really excited that the core devs seem to agree and are adding tablestakes features to core- the new default colorscheme, Treesitter WASM, and better commenting will all make my config even simpler!

At some point I might even try LSP integration again!

[WhyNotHugo]

> That works for a while, but like clockwork, something breaks- a plugin updates incompatibly, Neovim updates incompatibly, an external binary the plugin relies on updates incompatibly...

Just avoid upgrading plugins until necessary. I've no idea how old some plugins are; I only upgrade when necessary (e.g.: when neovim upgrades, or when I need some new feature).

[eptcyka]

My vim config is generated by nix, if I don’t break it, it does not break.

[marinhero]

Have you tried using an nvim distribution? They take care of all the plugin loading, config and testing. They stay reasonably updated too.

[bbkane]

I tried using LazyVim, but I didn't put much effort customizing it so I missed my custom config and I found it somewhat janky

[scutrell]

I think they are a good middle ground, but you're still left with some of the busy work. Further, you're a bit more at the mercy of the maintainer. Likely, Lazyvim isn't going anywhere, but it isn't out of the realm of possibilities either.

[whinvik]

What distribution would you recommend?

[nop_slide]

I recently started with Kickstart paired with this video, it's really easy and beginner friendly.

https://github.com/nvim-lua/kickstart.nvim

https://www.youtube.com/watch?v=m8C0Cq9Uv9o

[EasyMark]

I think lazyvim is one of the more successful/dependable ones

[desdenova]

I just use CoC for all LSP functionality, and everything just works with almost no issues.

Configuring the native LSP client is still too clunky to switch.

[EasyMark]

this is why I only update once a year or so around the beginning of the year. I mean "bit rot" is a real phenomenon but not in a year's time. If it fails. I just go back to my old config that is backed up in the cloud. If it fails, I can try again in a month. I'm too old to constantly be tinkering every week or two and hoping it doesn't break.

[tristan957]

I haven't used it, but vscode-neovim might give you the best of both worlds.