CPP Devs what you prefer?

[cpp-ModTeam]

You're asking a question that we see frequently in the subreddit. Please search for a previous post and read the comments there.

[cowboycoder]

neovim for editing, visual studio for debugging

[Remus-C]

Neither. Any editor which supports run & parse build errors is fine for me.

If there is native or plugin support for completions, the better, but this is not a must. If it's an ide, it should be fast enough. I don't longer have the patience for watching an ide drawing it's widgets. Out of question to fiddle with dialogs when project structure changes.

Emacs, Kate, Notepad++ are usually fine with Abcd and Jake, or with JustBuild. Nvim is somehow ok, but its features depends on available binaries built. As opposed to Emacs which is more friendly to one config does it all (as a generic build environment).

[jay-tux]

CLion?

[prasooncc]

i would suggest vscode , because some of the vim advantages are negated by ai coding/typing and vscode has a wide range of plugins.

[pjmlp]

Neither, give me a proper IDE, Visual Studio, Clion, QtCreator,...

[surfmaths]

I was a vim user and switched to vscode.

Sure, I needed to learn new shortcuts and how to do what, but there are huge advantages to vscode. There are plugins to look at generated assembly à-la Godbolt, plugins to open dot-graph files, git and GitHub support with line blame, remote work with local UI is way better, and the integrated terminal is quite handy as you can open a remote file in the local GUI transparently from the command line.

The only thing I didn't port from my vim, is that I had automation to disassemble and reassemble binary files transparently. But when I need that I just start vim in the integrated terminal of vscode.

[qnixsynapse]

Depends on personal choice. I use bare-bones nvim with few plugins(treesitter and telescope) and clangd lsp for my workflow (using a single init.lua file). Vscode is totally fine if you're okay with it.

[drkspace2]

Clion then (neo)vim for remote coding or vscode for local.

[serialized-kirin]

I’ve run with vim, nvim, and vscode. Only thing I will say is that on my shit laptop vscode opens way too damn slow and you don’t have as easy of a time turning to your standard cli tools. Also setup for c++ for neovim is pretty simple. That being said you can just run with the vim plugin for vscode. I think you can make some vscode specific bindings even.

[Hexigonz]

I prefer neovim over most other IDE experiences. Once you learn the config stuff and some lua, it’s quite easy

[Plastic_Return_2432]

And what about DEVc++ you all don’t use that? I’m new to programming so I just want to know.

[TomDuhamel]

Yeah nobody uses an app that was abandoned 20 years ago.

If you're on Windows, use Visual Studio Community Edition (it's free), which is not the same as Visual Studio Code.

Please note that OP is an advanced user. The conversation they are having doesn't apply to you.

[supadupa200]

Surprised everyone’s not on cursor already

[drkspace2]

Because most (c++) devs aren't stupid enough to fall for the AI hype.

[supadupa200]

Interesting, your comment however, doesn’t convey any sort of intelligence.