2 ms·
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.
by majewsky 11y 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 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?")