433
Devs sound alarm after Microsoft subtracts C/C++ extension from VS Code forks
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Apr 2025
433 points (97.6% liked)
Programming
19842 readers
353 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 !webdev@programming.dev
founded 2 years ago
MODERATORS
Plus you can always just use clangd. Its what I've always used with every text editor that has LSP support.
Honestly moving to clangd has got to be the single best thing I've done in C++, it's cross platform and I've found it to be significantly faster, more reliable, and more featureful than Microsoft's C++ plugin by a long shot
I havent used vscode in while but I do remember having a lot of issues with the Microsoft C++ plugin, especially in large projects. I switched to clangd very quickly.
Clang is a better C++ compiler than msvc, it generates faster binaries and can compile complex code that msvc errs on at least in my experience YMMV.
I wish there was a GCC equivalent; but even if clang is a corpowhore project it's atleast OSS