I hear this argument regularly, which is confusing when IntelliJ is free? It _has_ a paid version, but in the ~7 years that my employer was paying for the Ultimate Edition, I never once used any of them.
> is more resource efficient believe it or not
Sure, anecdotally this does seem to be true (by the fact that I can have VS Code and Factorio open at the same time :P ).
But the way you hear VS Code fans rave about it, you'd think there are oodles of extra functionality, not just "it's a little more efficient, but not so as you'd notice during the work day".
Let's say a license is worth about k hours of development time per year. Over the course of 1 year, IntelliJ will save you much more than k hours of development time.
On the other hand, you have VS Code, which needs over k hours to configure in order to get a fraction of what you can achieve with IntelliJ. You paid the same money in a different way and obtained less benefits.
I'm sure it's better for java though, haven't tried that.
Do you mean what Gateway does, or something else?
(I'm not a fan of the concept, but I think Jetbrains does it).
It’s standard for many projects which is why you use vscode.
I'm using this on a daily basis: https://www.jetbrains.com/remote-development/gateway/
It's not the same thing?
In contrast, almost all extensions work just fine in VScode remote, and you can sync your settings across all machines that you have without doing anything.
It's not really something jetbrains can do about it, but there's also the fact that vscode is almost a standard for one click remote dev so Gcloud, AWS and Azure integrate with it super well. I can access any machine on a single click, and open test envs too while having my settings synced on the browser too. Gateway being proprietary probably makes such integration impossible
Maybe I'm being naïve here, but - why would you need your IDE to have access to remote servers? From a quick look at the landing pages for Gateway it looks like this is basically setting up an ssh connection to a remote server so that you can run your IDE locally but edit files on another server - why would that be advantageous? The only thing I can think of would be if your development machine isn't powerful enough to run your tests or a development version of your code, but I can't imagine that's particularly common?
Like you I'm not actually convinced it's a useful feature generally (otherwise we'd still all be using X11), but those are some justifications.
Ah, this was the bit that I was missing. Thanks! That's.....certainly a constraint within which this feature could be useful. Seems extraordinarily niche, though!?
Like I said, I don't like the approach, it's way too "thin client" for me, but it seems to be part and parcel of our "towers of abstraction" approach to software development. I guess the next logical step is to abstract away the physical location of the code.
A lot of people have Mac/Arm dev machines, but deploy to Linux/x86 machines. Developing and testing on the hardware/OS you are targeting lets you avoid nasty surprises down the line.