2 ms·

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

by urthor 4y ago

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 "nvim distribution" via Patreon at this point. Configuring Vim to catch-up with Intellij is becoming a part time job.

alwillis 4y ago
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 with any IDE. That's not the point. What's great about Neovim and similar projects: there's a middle ground between a full-blown IDE and a "text-editor". Just because a coder/developer wants some nice things like autocompletions, diagnostics, refactoring and semantic formatting and syntax highlighting doesn't necessarily mean they must use a IDE, especially when some of the underlying technologies for providing these features (Treesitter, Language Server Protocol) are exactly the same. It won't take long for text editor users--Vim, Neovim, emacs, Hexlix--to expect these capabilities. It'll just become the norm. Just like how most young people today know a world without the internet being everywhere, we'll have users who've never known a time when every decent text editor didn't have what old-timers call "IDE" features.
- urthor 4y ago
  > 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.

by urthor 4y ago

alwillis 4y ago

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 with any IDE. That's not the point. What's great about Neovim and similar projects: there's a middle ground between a full-blown IDE and a "text-editor". Just because a coder/developer wants some nice things like autocompletions, diagnostics, refactoring and semantic formatting and syntax highlighting doesn't necessarily mean they must use a IDE, especially when some of the underlying technologies for providing these features (Treesitter, Language Server Protocol) are exactly the same. It won't take long for text editor users--Vim, Neovim, emacs, Hexlix--to expect these capabilities. It'll just become the norm. Just like how most young people today know a world without the internet being everywhere, we'll have users who've never known a time when every decent text editor didn't have what old-timers call "IDE" features.

urthor 4y ago
> 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.