• there’s nothing scary about the command line
  • developers like it because it can be faster, takes less work, and easier to automate
  • there’s also a whole community dedicated to getting you up to speed with Linux: [email protected]
  • that being said, on most modern distros, there’s no real need to ever leave the desktop anymore
• and you can still use VS Code on Linux or you can go one of the open source builds of VS Code: VSCodium or Code OSS

My understanding of Linux programming is that it’s mostly done in a code editor, then compiled on the command line.

That's not really true. You can do that, but with most IDEs (and some text editors) you really don't need to do that. You can do everything from the IDE.

I’m aware that cmake exists, and I’ve used it a bit, but I don’t like it. VS lets me just drop a .h and .cpp file into the solution explorer and I’m good-to-go. Is there really no graphical alternative for Linux?

It depends on the IDE and how it handles project files. Nowadays Qt Creator for example can just create your source code files and automatically add them to the generated project CMake. I'm pretty sure other IDEs or text editors have this functionality when paired with CMake or Meson too.

It must be noted that if the IDE has some custom project file manager (like Visual Studio does with sln and vcproj files) and you use it exclusively, you'll likely restrict your project to one platform and one IDE. Using something like CMake or Meson will make it easier to do crossplatform development and will let your users build the project without needing that specific IDE.

Personally I like modern CMake, the problem is that you'll see a lot of projects in the wild doing old CMake style, which is awful. Meson is okay, although it feels very Pythonic to me and lacks some features I use for Qt stuff.

There are IDEs for Linux as well and IMO it is unfair to compare IDE vs non-IDE workflows without also looking at the advantage in terms of automation, flexibility and the sheer endlessnes of customization options (e.g. through NeoVIM or Emacs).

You do not have to switch to Linux to get a hang of your Linux development though. Download a 30 day trial of CLion and develop a simple application that can be run in a Linux based container.

Regarding CMake, modern CMake not half as bad. CMake is also cross platform, you actually use it to generate your build files, your target could even be Visual Studio. For Linux it will most likely be a Makefile that you will then use to compile (with GCC or Clang) your code to objects which it will then link to create the binary.

There are also alternatives to CMake, namely Bazel and Meson, but I haven't used them yet.

Once you get the hang of it, you will have a deeper understanding of the language and that will help you in the long run.

CMake will also allow you to use Conan, that makes dependency management even easier.

You might be looking for CLion.

How exactly do you debug code when your build process is separate from your code editor? Having to compile my code, run it until I find a bug, then open it up in a debugger and start it all over sounds extremely inefficient.

There's a lot of incorrect assumptions baked into this. While you may choose to invoke your debugger separately from your editor, many modern editors support the Debug Adapter Protocol (DAP). This is a protocol developed by Microsoft for VSCode, and the VSCode debugger is quite powerful. I've only used Visual Studio many years ago, but from what I recall, the VSCode DAP is essentially just as powerful. And if you're not interested in VSCode, the Helix editor and probably NeoVim also support DAP.

how to make the transition from a Visual Studio user to a Linux programmer

You are also coming in with the constraint of programming in C++. For this specific language, I think I agree with others here that either CLion or VSCode+CodeLLDB are your best options today. Maybe after you get comfortable in the Linux environment, if you want to try something more keyboard-centric, install a Vim emulation plugin or even jump right into Helix or NeoVim.

I'm stuck working on windows at $currentCompany, and my experience with visual studio is that every other IDE I tried is:

1. More stable
2. Faster
3. More intuitive UI wise (well not all but most)

Clion is generally much more flexible and with better features.

Regarding SLN files vs cmake, well, I'd like to know how you deal with them, because the "GUI" that vs is struggles to deal with property sheet so hard I've resorted to using wsl to grep for whatever files add the dependencies that I need. Also, the idea of filters to show the code in a structured would be smart if, you know, filesysyems did not have directories. Oh and with cmake adding a file does not require adding 5 GUIDs in 10 different XML files for every single configuration.

I think the only thing I prefer in VS is that you can debut multiple targets at once, but I have not looked whether clion can do that

Install VSCodium, install g++ and gdb, have fun.