4 ms·

To list few of the new features: Asynchronous I/O support, channels (Vim can now exchange messages with another process in the background asynchronously), Backg

To list few of the new features: Asynchronous I/O support, channels (Vim can now exchange messages with another process in the background asynchronously), Background jobs, timers, packages for plugins! Wow! This is huge. So many interesting features landing on Vim 8.0.

andrewstuart2 10y ago
Async I/O, plus JSON is seriously enormous. I'm very excited for how much faster things will be, and I can imagine JSON support will definitely make integration just that much easier. My one minor gripe was plugin speed, as syntax highlighting, linting, etc. can take long enough to be jarring.
- ecthiender 10y ago
  Exactly!
- userbinator 10y ago
  Async I/O? In a text editor, where the bulk of the time is spent waiting for the user to do something? I've used (an older version of) Vim on huge 100MB+ files and never thought it to be slow at all. In fact I don't think I've ever experienced any lag with Vim. I suspect you won't find this new version any faster.
  - BonsaiDen 10y ago
    This is mostly about linters, makeprg's and things like Ctrl+P / Command+T, git-gutter etc. I recently switched to NeoVim and it really _does_ make a world of difference, saving is a whole lot faster when git-diff can be performed asynchronously and the ability to scan directories in the background makes fuzzy searching of files a lot faster.
  - chronial 10y ago
    This is in fact fixing a massive pain point in vim, and one of the main reasons why NeoVIM has so much support. Saving a file in vim takes 1-2 seconds for me. Not because my disk is slow, but because I run some linters on my files, that take that long to all complete. Async I/O is not about disk I/O, but communication with other programs.
  - hollander 10y ago
    I've opened 5GB files in Vim, on an average 2010 Ubuntu desktop. It took some time, like 5 minutes, but it worked.
- majewsky 10y ago
  Especially Syntastic. It's always a pain when every ":w" of a Ruby file hangs for 5 seconds during syntax checking because Ruby is so abysmally slow.
  - dopamean 10y ago
    Five seconds?! Mine hangs for at most half a second (and I thought that was a lot). I almost don't even notice it anymore.
    - jmedefind 10y ago
      I get long hangs (5 secs) when saving Ruby code. I think it just takes a long time to load up all the gems rubocop relies on, then to process the syntax. I put the blame squarely on Ruby, not vim.
    - majewsky 10y ago
      Let's say these are five perceived seconds. The number might or might not be skewed by my passionate hatred of Ruby.
  - andrewstuart2 10y ago
    Yeah, Syntastic is my number one offender. I'd love to see Syntastic be able to just maintain a background server linting process (or several). I can imagine that alone, skipping all the environment loading/code parsing, would likely be good enough to make all but the longest files lint fast enough to be unnoticeable.
    - andrewstuart2 10y ago
      (Still worth it by far, though. I'll take a few seconds and nice error highlight over an hour of "Where the heck is my missing semicolon?")
wodenokoto 10y ago
> Asynchronous I/O support I don't keep myself much up to date on these things, but wasn't this one of the main new features in NeoVim? (then code cleanup, then more language to script in)
- ecthiender 10y ago
  Yes it was. And now Vim is getting those features as well.
  - caipre 10y ago
    Are they merging code from neovim, or is it a parallel implementation?
    - Ericson2314 10y ago
      I think the former---from what I've heard neovim and vim are on very good relations, and here is the fruit of that.
      - levemi 10y ago
        Negative. NeoVim does away with supporting the ancient systems that are important to Bram for some reason. I seriously doubt they will merge.
        Ericson2314 10y ago
        Good relations =/=> must plan to unfork, at least in a post-git world.
    - oblio 10y ago
      Parallel. Bram (Vim maintainer) doesn't seem to like Thiago (Neovim lead dev).
  - superskierpat 10y ago
    Well except for the code cleanup and the more extensive scripting options ;) I've been a happy neovim user for a few months now, but I'm still glad to see that vim is keeping itself up to date.

andrewstuart2 10y ago

Async I/O, plus JSON is seriously enormous. I'm very excited for how much faster things will be, and I can imagine JSON support will definitely make integration just that much easier. My one minor gripe was plugin speed, as syntax highlighting, linting, etc. can take long enough to be jarring.

ecthiender 10y ago
Exactly!
userbinator 10y ago
Async I/O? In a text editor, where the bulk of the time is spent waiting for the user to do something? I've used (an older version of) Vim on huge 100MB+ files and never thought it to be slow at all. In fact I don't think I've ever experienced any lag with Vim. I suspect you won't find this new version any faster.
- BonsaiDen 10y ago
  This is mostly about linters, makeprg's and things like Ctrl+P / Command+T, git-gutter etc. I recently switched to NeoVim and it really _does_ make a world of difference, saving is a whole lot faster when git-diff can be performed asynchronously and the ability to scan directories in the background makes fuzzy searching of files a lot faster.
- chronial 10y ago
  This is in fact fixing a massive pain point in vim, and one of the main reasons why NeoVIM has so much support. Saving a file in vim takes 1-2 seconds for me. Not because my disk is slow, but because I run some linters on my files, that take that long to all complete. Async I/O is not about disk I/O, but communication with other programs.
- hollander 10y ago
  I've opened 5GB files in Vim, on an average 2010 Ubuntu desktop. It took some time, like 5 minutes, but it worked.
majewsky 10y ago
Especially Syntastic. It's always a pain when every ":w" of a Ruby file hangs for 5 seconds during syntax checking because Ruby is so abysmally slow.
- dopamean 10y ago
  Five seconds?! Mine hangs for at most half a second (and I thought that was a lot). I almost don't even notice it anymore.
  - jmedefind 10y ago
    I get long hangs (5 secs) when saving Ruby code. I think it just takes a long time to load up all the gems rubocop relies on, then to process the syntax. I put the blame squarely on Ruby, not vim.
  - majewsky 10y ago
    Let's say these are five perceived seconds. The number might or might not be skewed by my passionate hatred of Ruby.
- andrewstuart2 10y ago
  Yeah, Syntastic is my number one offender. I'd love to see Syntastic be able to just maintain a background server linting process (or several). I can imagine that alone, skipping all the environment loading/code parsing, would likely be good enough to make all but the longest files lint fast enough to be unnoticeable.
  - andrewstuart2 10y ago
    (Still worth it by far, though. I'll take a few seconds and nice error highlight over an hour of "Where the heck is my missing semicolon?")

wodenokoto 10y ago

> Asynchronous I/O support I don't keep myself much up to date on these things, but wasn't this one of the main new features in NeoVim? (then code cleanup, then more language to script in)

ecthiender 10y ago
Yes it was. And now Vim is getting those features as well.
- caipre 10y ago
  Are they merging code from neovim, or is it a parallel implementation?
  - Ericson2314 10y ago
    I think the former---from what I've heard neovim and vim are on very good relations, and here is the fruit of that.
    - levemi 10y ago
      Negative. NeoVim does away with supporting the ancient systems that are important to Bram for some reason. I seriously doubt they will merge.
      - Ericson2314 10y ago
        Good relations =/=> must plan to unfork, at least in a post-git world.
  - oblio 10y ago
    Parallel. Bram (Vim maintainer) doesn't seem to like Thiago (Neovim lead dev).
- superskierpat 10y ago
  Well except for the code cleanup and the more extensive scripting options ;) I've been a happy neovim user for a few months now, but I'm still glad to see that vim is keeping itself up to date.