3 ms·
I want to believe this, but my experience with VSCode generally goes like this: I find a bug in a tool I rely on or want to make a PR with some feature I think
by stinos 4y ago
I want to believe this, but my experience with VSCode generally goes like this: I find a bug in a tool I rely on or want to make a PR with some feature I think could be generally useful. Turns out the tool uses a language I've not used before, or requires me to test for multiple platforms, or something. In any case I have to start from scratch. So I just lookup 'how to X in VSCode' and/or open VSCode, go to Extensions. Follow some simple instructions, get what's needed and a couple minutes later I'm developing. And fairly decent step-by-step debugging + watch windows and whatnot. And debugging remotely on another platform. And sometimes VS Code then also offered to install the complete toolset needed on that platform.
Now, maybe I've just been lucky, or toolsets just got better overall, or maybe I've missed something, but when I did this 20 years ago there was a good chance I was looking at a non-trivial amount of research, finding tools, fiddling with config files, text-based debugging at best sometimes or hideous IDEs, etc. So alternatives exist, one can call them respectful, but turns out for a couple of usecases that's besides the point: the experience for one-off 'let me just quickly try this in whatever is the cool language of the day' is, as far as I'm aware, simply unsurpassed. And that's the strength for me. Not sure if I'd be paying for that, but right now it's just what it is.