3 ms·

Language-servers make the choice of IDE moot. My vim setup is just as capable with typscript as vscode.

by root_axis 7y ago

_bxg1 7y ago
They don't completely. They help a ton, but certain IDEs are designed holistically with certain use-cases in mind and have very specific features that lend themselves to those use-cases on top of the basic error/autocomplete language support. For example, the Rust extension in VSCode gives me an inline button next to any function that's annotated as a test, which I can click to run that test. That's really useful and really specific to Rust. Whereas other IDEs (or other IDE extensions) might just do a bare-bones language server hookup to show errors and that's it.
- root_axis 7y ago
  > For example, the Rust extension in VSCode gives me an inline button next to any function that's annotated as a test, which I can click to run that test Not an ideal example. The rust-vim plugin supports the same feature (though, naturally via keys instead of mouse). https://github.com/rust-lang/rust.vim https://github.com/rust-lang/rust.vim
- fjp 7y ago
  VSCode isn't there yet for Python refactoring - I still find myself needing to find and replace to get everything when I rename a symbol or move a package (breaking imports). I should never have to do that. Pycharm refactors Python flawlessly. I would love to be exclusively in VSCode because of its configurability & overall snappiness but it's just not there for Python
  - _bxg1 7y ago
    My point exactly. VSCode was purpose-built with TypeScript in mind, IntelliJ was purpose-built with Java in mind (it's right in the name), Pycharm was purpose-built with Python in mind. It's great when an editor supports several languages, but it's probably going to support one or two of them better than the rest, so you want to pick yours based on what you spend most of your time in.

3 ms·

Language-servers make the choice of IDE moot. My vim setup is just as capable with typscript as vscode.

by root_axis 7y ago

Language-servers make the choice of IDE moot. My vim setup is just as capable with typscript as vscode.

_bxg1 7y ago
They don't completely. They help a ton, but certain IDEs are designed holistically with certain use-cases in mind and have very specific features that lend themselves to those use-cases on top of the basic error/autocomplete language support. For example, the Rust extension in VSCode gives me an inline button next to any function that's annotated as a test, which I can click to run that test. That's really useful and really specific to Rust. Whereas other IDEs (or other IDE extensions) might just do a bare-bones language server hookup to show errors and that's it.
- root_axis 7y ago
  > For example, the Rust extension in VSCode gives me an inline button next to any function that's annotated as a test, which I can click to run that test Not an ideal example. The rust-vim plugin supports the same feature (though, naturally via keys instead of mouse). https://github.com/rust-lang/rust.vim https://github.com/rust-lang/rust.vim
- fjp 7y ago
  VSCode isn't there yet for Python refactoring - I still find myself needing to find and replace to get everything when I rename a symbol or move a package (breaking imports). I should never have to do that. Pycharm refactors Python flawlessly. I would love to be exclusively in VSCode because of its configurability & overall snappiness but it's just not there for Python
  - _bxg1 7y ago
    My point exactly. VSCode was purpose-built with TypeScript in mind, IntelliJ was purpose-built with Java in mind (it's right in the name), Pycharm was purpose-built with Python in mind. It's great when an editor supports several languages, but it's probably going to support one or two of them better than the rest, so you want to pick yours based on what you spend most of your time in.