4 ms·
I switched from a JetBrains IDE to VS Code for one reason: I don't want to build a C++ codebase on my laptop. It requires a lot of processing power, takes a lon
by shitlord 5y ago
I switched from a JetBrains IDE to VS Code for one reason: I don't want to build a C++ codebase on my laptop. It requires a lot of processing power, takes a long time, kills the battery, and makes the fan go off.
I'm willing to use VS Code Remote and sacrifice some features to not have to deal with that. My employer doesn't really care if I provision a big EC2 instance for development. I'll take a look at Fleet a little later on.
- ta988 5y agoJetbrains now has a remote agent, works decently.
- Liquid_Fire 5y agoI've tried all of JetBrains' remote working solutions (there are confusingly many now, 3-4?) and they all seem unusable for my use case, where VSCode (or indeed ssh + vim) just works. And my use case is not particularly special, C++ with CMake and some wrapper scripts to pull in dependencies. The only solution that works OK is Projector, but I can achieve the exact same thing but less buggy with VNC.