If my IDE is anything heavier than VSCode well you can fuck right off with that. I’m a DevOps engineer so it’s easy for me to be so religious (running YAML in VSCode - lulz)
Then why would you write something like if you aren’t using the CLI you’re doing it wrong?
You made it sound like you’re a Vim warrior or something which, if true, you have a much higher pain threshold than I do.
"Build" is the operative word here, in the classic programming sense:
Edit using whatever you want. The process to build <e.g. compile your C application> should be CLI-only, primarily for automation purposes, and to decouple you from the IDE, which may or may not generate build scripts.
Well, unless your ide has an integrated CLI as VSCode does in which case it’s all ponies and rainbows.
Basically, I live in VSCode even when I’m accessing instances in AWS, etc or WSL.
It used to be that IDEs were designed to do everything for you, including the build, and most of them still do this. This made automation difficult or impossible, because starting an IDE and clicking buttons in automated tests is .. problematic.