this post was submitted on 22 Jul 2024
104 points (92.6% liked)

Programming

17001 readers
262 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
104
submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/[email protected]
 

I have not used an IDE since I ditched Turbo Pascal in middle school, but now I am at a place where everyone and their mother uses VS Code and so I'm giving it a shot.

The thing is, I'm finding the "just works" mantra is not true at all. Nothing is working out of the box. And then for each separate extension I have to figure out how to fix it. Or I just give up and circumvent it by using the terminal.

What's even the point then?

IDK maybe its a matter of getting used to something new, but I was doing fine with just vim and tmux.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 1 month ago (2 children)

Depends on the language. C/C++/C# I never manage to make it work. Rust works incredibly well. Python needs some small fixing on the paths but works good too. Java needs a lot of fixing, sometimes I make it work, others not.

C# and java are both much easier to set up in an IDE (VS and eclipse (ew)) respectively. C/C++ are just hard to set up, I don't think it's much harder than CLion.

So except java and C#, every language is as easy to set up as any other editor/IDE.

I only use vim to edit config files through ssh, so I don't know how it works for actual development. However, I doubt it is easier than vs code.

[–] [email protected] 9 points 1 month ago

For C++ I found the clangd plugin to be the secret. Just install that and get your build to output a compile_commands.json in your build folder. That is easy to do with cmake but most other setups can do it too. The plugin will find that after a clean build. Then it will magically index your whole project.

[–] gears 1 points 1 month ago

I use vscode everyday with gdb and gcc (and gdbserver.) it works well, but does require some set up.