Hacker News new | ask | show | jobs
by rugina 1002 days ago
Tried it and it feels slow. I opened a Rust project and after a long wait to index crates, I opened a file and deleted a commented line. It took a few seconds to display the annotations again.

While waiting, I did some work in neovim.

1 comments

FWIW, I've had the same experience with CLion at my previous job. Syntax highlight lagged 30+ seconds behind. Autocomplete was unusable, because it took almost a minute sometimes (for method names!!), or would pop up with stale/irrelevant results. Everything in the UI felt sluggish. Used an ungodly amount of RAM. Plugins would randomly stop working and require me to reinstall them to work.

The only thing going for it was that the debugger worked better than gdb (although I think it uses GDB unde the hood, but probably does something better than when I manually fiddle with gdb)

VS Code is sometimes a bit sluggish when handling input. Don't know why, and it only happens on my Macbook Air, (so might be thermal throttling?) but it happens rarely.

The nice thing about Code is that it's also easier to work across multiple languages without having to switch tools.

However, it does say it's still in preview, so it might get better?

Also, the UI looks radically different (and nicer) than what CLion looked like, so maybe they have a new UI framework that fixes some of the problems I had with CLion