this post was submitted on 10 Sep 2023
5 points (85.7% liked)

C++

1773 readers
1 users here now

The center for all discussion and news regarding C++.

Rules

founded 1 year ago
MODERATORS
top 11 comments
sorted by: hot top controversial new old
[–] lysdexic@programming.dev 4 points 1 year ago
[–] chinstrap@lemmy.ml 4 points 1 year ago
[–] KindaABigDyl@programming.dev 3 points 1 year ago
[–] wosrediinanatour@mastodon.social 2 points 1 year ago (1 children)

@lysdexic TMUX & VIM & clangd & vim-ale & fzf.vim

[–] lysdexic@programming.dev 1 points 1 year ago (1 children)

Would it be fair to represent that as simply vim?

[–] lysdexic@programming.dev 2 points 1 year ago

Visual Studio (2022, 2019, 2013, etc)

[–] lysdexic@programming.dev 2 points 1 year ago

Visual Studio Code

[–] lysdexic@programming.dev 1 points 1 year ago
[–] DaleGribble88@programming.dev 1 points 1 year ago (1 children)

Visual Studio - not VSCode. It is heavy AF, but that debugger and profiler are just too good not to use. I also don't want to fight against a million compiler/makefile/configuration issues. I just want something that works, and Visual Studio just works.

All that said, I've probably written more C/C++ in Vim on a Linux box since I prefer C# when working on Windows, so idk? Visual Studio on Windows and Vim on Linux distros.

[–] lysdexic@programming.dev 2 points 1 year ago* (last edited 1 year ago)

Visual Studio - not VSCode.

Please upvote Visual Studio then.

It is heavy AF, but that debugger and profiler are just too good not to use.

I agree.

I also don’t want to fight against a million compiler/makefile/configuration issues.

Visual Studio does not prevent us to get ourselvss in trouble, though. CLion + CMake is the only combination of IDE and build system that I know that is problem-free, and even so it requires a lot of discipline to keep the cmake project simple.