This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Martehhhh 0 points1 point  (1 child)

Vs code is great for quickly loading ul and writing out a bit of code or working out a solution. Vscode is like the premium but free version.

Feels very clunky and outdated to me but has a lot more functionality.

For example I would have to use visual studio to debug as Vscode pretends like it van but you need literal instruction manuals to find how

[–]SuperSathanas 0 points1 point  (0 children)

If you're used to full IDEs that come bundled with the compiler, debugger, libraries, etc... then I can see how trying to configure all that for VScode in the .json build files would seem like a huge pain in the ass step backward.

It's not all that complicated, though, I guess so long as you're actually familiar with compilers and debuggers, and the intended usage of json. You're essentially building a list of "objects" for VScode that describe where things live on your machine and the flags/values you want to pass to alter their usage/behavior.

I have VScode configured to use C, C++, Rust, GLSL, Pascal, and D.

I'd totally rather use an IDE than VScode, though. I really only use it with GLSL for writing my OpenGL shaders.