3 ms·

I think (neo)vim has many years ahead, but also think the market overlaps with vscode. I believe that, for the average users, defaults, including a default plug

• AlexSW 3y ago
  The overlap with VS Code is very helpful for Neovim too though, as Neovim integrates well with technologies and plugins intended for VS Code. My C++/Rust debugger setup comes from installing VS Code, getting it to install its debugger, and then pointing Neovim at it.
• rockwotj 3y ago
  Yeah I feel like if you don’t want to spend time tweaking configs then vscode is just the better option.
  • vivekd 3y ago
    I don't think you're really meant to tweak configs much in neovim. Just get a basic config file off GitHub and then update here and there as you find stuff you like/need. I know that sounds complex but if you're coding (which I assume many neovim users are) should be fairly straightforward
    • PKop 3y ago
      That sounds like tweaking configs
  • myaccountonhn 3y ago
    Or helix is a good option.
• lawn 3y ago
  I have a hard time buying the argument against changing defaults. I do get that the Vim editing model is hard, but that professional developers refuse using a tool because you have to change some defaults and customize it a little is too much. It's really not that hard or time consuming to setup, for more gains than many of the courses or experiences people have put themselves through. And it's not like it's a "vscode vs Vim" thing, I see the same argument inside the Vim community too where people refuse plugins because it's too much work, or even switch to Vim-like editors that don't have a plugin system as if it was a positive thing. What gives? I'm sure it's not as easy as everyone just being lazy.
  • eviks 3y ago
    if you deny reality (it's hard and time consuming), you won't buy its outcome
    • lawn 3y ago
      Is it? Using a Neovim setup like LazyVim is really fast and easy. Even something like kickstart.nvim is quick and easy. Maybe it's the perseption that it's hard and time consuming that's the problem?
      • eviks 3y ago
        Yes, it is. First, how would you know that LazyVim is the fast and easy one? Second, it's not fast and easy even with LazyVim, let's start with the basics like keymap: map({ "n", "x" }, "j", "v:count == 0 ? 'gj' : 'j'", { expr = true, silent = true }) map("n", "<C-h>", "<C-w>h", { desc = "Go to left window", remap = true }) To understand this (and to adjust to your liking) you kind of have to learn the language you're not going to use ('gj' or <C-w>h) instead of using something easily readable like ["go","window","left"], or instead of actually pressing C-w to insert <C-w> like many (mostly GUI) apps allow Then the time consuming part: it doesn't make it easy to resolve conlficts which inevitably arise when doing many rebinds. Also, it'd be very time consuming to learn and reference that unused binding language Then the help is rather verbose and not intuitive (see my parent comment) (don't remember if help uses default keybinds or actual ones Then it relies on a very barebones and not very popular language (though miles better than vimscript) Then there are a gazillion of other things which make the perception reflect the reality pretty well