7 ms·
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
by andrewstuart2 11y 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 11y agoExactly!
- userbinator 11y agoAsync 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 11y agoThis 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 11y agoThis 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 11y agoI've opened 5GB files in Vim, on an average 2010 Ubuntu desktop. It took some time, like 5 minutes, but it worked.
- majewsky 11y agoEspecially 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 11y agoFive 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 11y agoI 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 11y agoLet's say these are five perceived seconds. The number might or might not be skewed by my passionate hatred of Ruby.
- andrewstuart2 11y agoYeah, 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 11y 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?")