3 ms·

VSCode has debugging built in and can connect to various runtimes. Not that I ever use that - I prefer sticking with the language native tools, and I rarely re

VSCode has debugging built in and can connect to various runtimes. Not that I ever use that - I prefer sticking with the language native tools, and I rarely require anything beyond inspecting runtime values and simple benchmarking. Maybe this comes from the perspective of Java, where you need an IDE to do proper debugging, building/starting an application requires a gazillion command line arguments, and you have layers upon layers of abstraction to drill through? Those are pains worth taking away, but don't apply to all languages or platforms.

Ygg2 5y ago
Recently CLion got decent Rust debugging. While I love rust-analyser and its integration with VSCode, the debugger in CLion is worth its weight in gold (like a ton or so). Would I prefer a native IDE for Rust? Maybe one that doesn't require 4GiB of Ram to operate? Yes. But bar for IDEs today is very high.
nwatson 5y ago
Refactoring, "show me where this class, function, variable is used", "show me a class hierarchy", "analyze my code and tell me where I'm not using best practices and suggest the best fixes and apply my selected one", are places where a full-fledged IDE shines. An editor won't do those, or most of those. A 15-minute task turns into a 20-second blip.
- ricardobeat 5y ago
  VSCode does all of the former, at least for the two main languages I work with, TypeScript and Go. Prettier, ESLint and golangci-lint handle the style checks. JetBrains says the problem is “users are unaware of what an IDE can do” but maybe it is the other way around?
  - gnufied 5y ago
    Currently I am using Emacs and Goland as my main IDEs/editors and have tried vscode but the thing is - what vscode can support entirely depends on what LSP server can support. This can make or break vscode. For example - both vscode/emacs (via lsp-mode) throw errors/warnings in multi-module go projects. Even worse, if you are hacking your build chain the way some projects like Kubernetes do(via staging directory), lsp-server refuses to work entirely in `staging/` directory of the project. I also saw that switching branches can confuse lsp-server. All of these problems are basically non-existant in Goland(Intellij).So depending on complexity of a project, I would day it is worth using an IDE.
  - Aeolun 5y ago
    What’s nice that Jetbrains does in Typescript that VSCode doesn’t is automated refactoring. I can change or move a function anywhere in my project and all references are automatically updated. VSCode does it to some extend, but the difference is night and day.
kaba0 5y ago
You mean like the 64000 packages required for a simple hello world with 34 vulnerabilities and ads, and what takes more time to “compile” for trivial AST-manipulations than a god-damn optimizing compiler do?
smrtinsert 5y ago
That last paragraph is wrong but I'm too tired to explain why for the millionth time.
- ricardobeat 5y ago
  I’d love to hear why. Would be the first time for me :)

Ygg2 5y ago

Recently CLion got decent Rust debugging. While I love rust-analyser and its integration with VSCode, the debugger in CLion is worth its weight in gold (like a ton or so). Would I prefer a native IDE for Rust? Maybe one that doesn't require 4GiB of Ram to operate? Yes. But bar for IDEs today is very high.

nwatson 5y ago

Refactoring, "show me where this class, function, variable is used", "show me a class hierarchy", "analyze my code and tell me where I'm not using best practices and suggest the best fixes and apply my selected one", are places where a full-fledged IDE shines. An editor won't do those, or most of those. A 15-minute task turns into a 20-second blip.

ricardobeat 5y ago
VSCode does all of the former, at least for the two main languages I work with, TypeScript and Go. Prettier, ESLint and golangci-lint handle the style checks. JetBrains says the problem is “users are unaware of what an IDE can do” but maybe it is the other way around?
- gnufied 5y ago
  Currently I am using Emacs and Goland as my main IDEs/editors and have tried vscode but the thing is - what vscode can support entirely depends on what LSP server can support. This can make or break vscode. For example - both vscode/emacs (via lsp-mode) throw errors/warnings in multi-module go projects. Even worse, if you are hacking your build chain the way some projects like Kubernetes do(via staging directory), lsp-server refuses to work entirely in `staging/` directory of the project. I also saw that switching branches can confuse lsp-server. All of these problems are basically non-existant in Goland(Intellij).So depending on complexity of a project, I would day it is worth using an IDE.
- Aeolun 5y ago
  What’s nice that Jetbrains does in Typescript that VSCode doesn’t is automated refactoring. I can change or move a function anywhere in my project and all references are automatically updated. VSCode does it to some extend, but the difference is night and day.

kaba0 5y ago

You mean like the 64000 packages required for a simple hello world with 34 vulnerabilities and ads, and what takes more time to “compile” for trivial AST-manipulations than a god-damn optimizing compiler do?

smrtinsert 5y ago

That last paragraph is wrong but I'm too tired to explain why for the millionth time.

ricardobeat 5y ago
I’d love to hear why. Would be the first time for me :)