Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Neovim 0.7 Released

github.com

Post reply on HN
Print view View original

31–40 of 220 posts

Re: Neovim 0.7 Released

#31

Post by LVB »

ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

I held this view too for quite a while. But in recent years as I’ve been exposed to some really powerful features in VSCode and GoLand, I’ve adopted a much more flexible workflow. I always have my CLI editor running and might spend the day in there, but I often have an IDE running in parallel (with Vim bindings, naturally). By now I automatically switch between the two based on whatever is the better platform for the immediate task, and have let go trying to load up Vim beyond basic LSP.

Re: Neovim 0.7 Released

#32

Post by capableweb »

gpanders wrote: post #24

I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/

Seems to be missing one of the bigger changes: support for python 2 has been completely dropped in favor of python 3.

Re: Neovim 0.7 Released

#33

Post by Barrin92 »

ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

Integration. The last time I tried neovim the LSP kept crashing for me on random occasions, some plugins had considerable performance issues, some things weren't async, and so forth.

Vscode or Jetbrains or any other integrated software is from the ground built up to have its tools work together 100% of the time. I like vim fine if I edit something without any plugins needed but otherwise I'll stick with an IDE. And if I want vim controls I'll just turn them on the IDE because conceptually for me it makes more sense to port keyboard controls to an IDE than to port the entire IDE to a terminal

Practical example, look at the instructions to set up an ide-like ocaml environment with neovim[1]. It requires basically to install half a dozen tools by hand and to fix the linter config before you've even started. In VsCode it's literally one click.

[1]https://www.rockyourcode.com/setup-ocaml-with-neovim/

Re: Neovim 0.7 Released

#34

Post by auslegung »

brightball wrote: post #18
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

One of these days I really need to sit down and commit to learning to use Vim at this level. I always use Vim when I'm editing from a terminal but generally stick with VSCode or the Jetbrains family of IDEs for any real coding projects. I've just never gotten around to learning vim in a more advanced way than edit, replace, copy paste, skip to line and search. Any good suggestions on where to start? I looked at Space…

I highly recommend following this author’s advice https://medium.com/actualize-network/how-to-learn-vim-a-four...

It’s a pretty gentle introduction to vanilla vim over 4 weeks. After that point I’d recommend using nvim and all the plugins you want to make life easier, but learning The Vim Way is very powerful

Re: Neovim 0.7 Released

#35

Post by ducktective »

People who have tried both vim and nvim:

- I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment?

- Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sitter is the better solution on this front

Re: Neovim 0.7 Released

#36

Post by ufo »

gpanders wrote: post #24

I did a brief write up on some of the biggest new features here: https://gpanders.com/blog/whats-new-in-neovim-0-7/

Thanks for summarizing the highlights!

The client-server part is the one I'm most excited about. It is one of my favorite things in kakoune and it'll be nice to have it on neovim too. I find it more intuitive to use separate terminal windows with all the usual window manager shortcuts, instead of using vim-specific terminal splits.

Re: Neovim 0.7 Released

#37

Post by lambdaba »

blowski wrote: post #5
ilovecaching wrote: post #3

I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I can edit the kernel with clangd and get hover reference, autocomplete, go to def, ref, dec, smart refactor, and that's on top of being able to easily jump and fix lint/bugs using Vim's already great support for parsing compiler errors. With term added (which is a core Vim feature) it also has excellent support for gdb debugging…

> I will never understand why people choose VSCode/Jetbrains over a terminal based editor. I don't want to use my valuable time learning how to get vim working in some super-optimal way that's hypothetically going to improve my productivity by 1%. JetBrains consistently works well enough for me that I'm not going to bother switching. 90% of my life is spent thinking about how to solve the problem so the editor is not…

The promise with Vim (and Emacs) is you'll never need to switch to something else, and the skills are transferable (script with Lua, keybindings very often available in other apps). Interestingly it has helped me most with cli stuff, I can edit command lines much quicker and have even configured a keybind my shell to open the command line in Vim for editing.

If a terminal-based workflow is not your thing it's a tougher sell.

Re: Neovim 0.7 Released

#38

Post by yjftsjthsd-h »

Brian_K_White wrote: post #9

neovim should not be named anything-vim for the same reason a Tesla is not a "neomaclaran".

It is literally a fork of the vim codebase, and the name clearly indicates that it has diverged. If Tesla had started with a complete copy of McLaren designs, then (aside commercial/trademark issues) it'd be 100% reasonable to call it a "Neo McLaren". (Obviously that wouldn't happen because businesses run differently from FOSS, but the principle is sound.)

Re: Neovim 0.7 Released

#39

Post by capableweb »

Brian_K_White wrote: post #9

neovim should not be named anything-vim for the same reason a Tesla is not a "neomaclaran".

Not sure how that's relevant here. Is Tesla (the cars) a fork of McLaren with changes after doing the fork?

Neovim is literally a vim fork, with .lua supported everywhere .vim is used and many other additions/changes/removals.

Re: Neovim 0.7 Released

#40

Post by stnmtn »

ilovecaching wrote: post #8
mbernstein wrote: post #4

Earlier quoted context omitted.

Neovim is amazing but recall how long it took you to get used to vim keybindings. It isn't something you master overnight. I recall it took me a few weeks to get comfortable. Lots of people are perfectly comfortable not using keyboard navigation. Edit: Also to note - vscode supports editing files anywhere over ssh as well, so there isn't a huge advantage to neovim there.

Except that I can use vim on my iPad Pro with just a terminal app, which I can't do with VSCode. Vim is portable anywhere you can get a terminal connection, even if it's over serial.

While it takes more work (and probably won't work over SSH), looks like there's a neat way to host a vscode server and use and Ipad as a client of it: https://medium.com/swlh/vs-code-for-ipad-and-other-phones-an...
Post reply on HN