I’d miss far too many of the features offered by true IDEs (especially WebStorm) to go back to vim... But damn it’s fast when set up right. That’s something I wish I could take with me.
-
-
Replying to @JofArnold
We've fixed some performance issues in upcoming WebStorm 2019.3: specifically, the IDE startup has been optimized, so WebStorm now launches faster. And we'll keep working in this direction next year. We hope it makes you feel a little bit better about the IDE's sluggishness
2 replies 0 retweets 1 like -
Replying to @WebStormIDE
Nice. Probably the greatest thing I'd notice is faster `eslint --fix`. Currently done via WebStorm using file watchers and it's probably 1/10th the speed of VSCode which I'm guessing does it internally? So slow I've usually changed the code by the time file changed and reloaded.
1 reply 0 retweets 0 likes -
Replying to @JofArnold
File Watcher runs a configured tool for every file on every saving. That's not the fastest approach for tools like ESLint but that's how file watchers work because by design they should be able to run any command line tool.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE @JofArnold
Please consider using the Fix ESLint Problems action: it is better integrated with ESLint (and doesn't start a new process) and it fixes problems in the current file. It's possible to assign it to a selected shortcut in Preferences | Keymap.
1 reply 0 retweets 0 likes -
Replying to @WebStormIDE
Thanks - I did see that. But I have to add an extra binding though, right? Not having it run as part of save isn't something I'd like to consider. I remember from my searching before that's not possible?
1 reply 0 retweets 0 likes
It would be possible to create a macro that would run save and fix actions and assign it to a shortcut. Sorry, there's no other way other than file watcher to run it on autosave.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.