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

Vim After 15 Years (2017)

blog.langworth.com

Post reply on HN
Print view View original

111–116 of 116 posts

Re: Vim After 15 Years (2017)

#111

Post by urthor »

alwillis wrote: post #72
urthor wrote: post #66

Sadly, the Vim/Emacs configuration burden is growing every year. IDE developers just keep inventing new tools. GitHub Copilot is the latest, who knows what's next? Especially for Rust, JVM & Java. Rust without a IDE warnings is... extremely difficult. Unless you're extremely practiced with it. As time goes on, feature parity with fully featured IDEs like Jetbrains is steadily becoming harder. I'd readily consider a "…

Configuring Vim to catch-up with Intellij is becoming a part time job. It doesn't have to be. I tried a bunch of things but LSP-Zero just works. The UI/UX for installing LSPs and linters, etc. is better than VS Code. As time goes on, feature parity with fully featured IDEs like Jetbrains is steadily becoming harder. As far as I can tell, there's no stated goal by anyone involved with Neovim to reach feature parity wi…

> What's great about Neovim and similar projects: there's a middle ground between a full-blown IDE and a "text-editor".

That's a perfectly fine goal.

I wrote the above in the context of so many comments saying "what's the point of an IDE."

There's absolutely a place for CLI text editors and REPLs.

I simply doubt they will ever replace the IDE as my collection of the more arcane JVM tools.

Re: Vim After 15 Years (2017)

#112

Post by myuzio »

statico wrote: post #34
statico wrote: post #29

Author here. Many will be disappointed to know that I've been using VS Code almost exclusively since 2019 (with the Vim plugin of course). I've been meaning to write a follow-up article, but unfortunately writing is low on the priority list. The main reason is that these days, when I _am_ coding, I mostly write TypeScript and React on my local machine (not much SSH these days), and VS Code Just Works™. I tried twice…

Another thing: I think I use VS Code more because I spend much less time in the terminal than I did 5, 10, or 20 years ago. Everything happens in the browser now. I used to write lots of tools and services and commands for myself based in the terminal, but now web-based tools have replaced most of them. Some notable examples of things I would have used the command line for a decade ago: - Gmail for email (I'll switch…

Same thing happened to me since 2021, weirdly enough my VIM setup was quite close to yours. Nowadays, I'm using VSCode + vim plugin, which is kind of the best of the two worlds.

What I miss however from the good-old development in Terminal days:

1. How distraction-free terminal is by default without all the popups and extra things on the screen

2. How I could do anything in my development environment without having a mouse

Therefore naturally I checked your dotfiles and I think I will try to adopt your keybindings. Thanks for sharing.

Re: Vim After 15 Years (2017)

#113

Post by jpcrs »

statico wrote: post #29

Author here. Many will be disappointed to know that I've been using VS Code almost exclusively since 2019 (with the Vim plugin of course). I've been meaning to write a follow-up article, but unfortunately writing is low on the priority list. The main reason is that these days, when I _am_ coding, I mostly write TypeScript and React on my local machine (not much SSH these days), and VS Code Just Works™. I tried twice…

I also recently migrated from nvim to VSCode (First with vim plugin, now with vscode-neovim plugin).

Probably I have the wrong mindset, but I've always tried to replicate a full IDE experience on nvim, and it was a frustrating experience because there was always something else missing, at the end I had to manage 30+ Plugins that could break at any time.

Even though the vim experience inside VSCode is far from perfect (really lacking when we compare with IdeaVim for example), it's a breath of fresh air being able to manage my plugins/lsp/etc with a single click.

The only thing that I miss daily is something like Telescope/fzf. VSCode fuzzy search works fine for file names inside the open project, but searching for file content/other projects/previous open files is really bad.

Recently tried to develop something similar on vscode just for fun (Even I don't use it tho, just accepted the limitation): https://github.com/jpcrs/Binocular

Re: Vim After 15 Years (2017)

#114

Post by omarelbie »

decafninja wrote: post #63

I would still love to learn vim if only for the nerd credentials. However I cannot imagine how I would reproduce the workflow to even come close to approaching my current productivity level with VS Code. I'd love to sit down with a vim expert for a day and see how much of my workflow I could replicate.

I use the Vim plugin within VScode. For me it's really the best of both worlds: Full-blown IDE features along with fast Vim editing. Highly recommend it!

Re: Vim After 15 Years (2017)

#115

Post by embeng4096 »

omarelbie wrote: post #114
decafninja wrote: post #63

I would still love to learn vim if only for the nerd credentials. However I cannot imagine how I would reproduce the workflow to even come close to approaching my current productivity level with VS Code. I'd love to sit down with a vim expert for a day and see how much of my workflow I could replicate.

I use the Vim plugin within VScode. For me it's really the best of both worlds: Full-blown IDE features along with fast Vim editing. Highly recommend it!

I also use VSCodeVim! One struggle I have though is that navigating with Ctrl+d / Ctrl+u or Shift+[ / Shift+] still opens folds if the cursor lands in the middle of a folded section. Do you run into this also and/or know a fix/workaround?

Re: Vim After 15 Years (2017)

#116

Post by cjvirtucio »

Trufa wrote: post #9

It's alway pretty fascinating to me that people can actually be productive without an IDE. I've tried several times Vim and I just don't get it how you can live without certain functionalities, I'm sure that with enough tinkering you can get pretty close but, for example, search seems to always be kind of a pain in the ass for the complex queries with regex through many files and stuff like that, specially the presen…

the main thing that allows me to be productive with "only" vim is, funnily enough, things outside vim: bash knowledge. search, for instance, I can usually do in flexible ways with a pipeline of commands.
Post reply on HN