380
Devs sound alarm after Microsoft subtracts C/C++ extension from VS Code forks
(www.theregister.com)
this post was submitted on 26 Apr 2025
380 points (97.5% liked)
Programming
19813 readers
902 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It looks like the extension is licensed under MIT https://github.com/Microsoft/vscode-cpptools You can "simply" fork it and provide builds yourself, right?
Not the case. There are binary components.
It doesn't matter though because the Clangd & CodeLLDB extensions completely replace it and are actually waaaaaaay better.
With Microsoft's C++ extension it always rinsed the CPU - there were files I had to avoid opening because then it would analyse them and I'd have to kill it. The code intelligence also seemed very "heuristic" and was quite slow.
Clangd fixes all of that. It's fast, doesn't choke on huge files, and if you have
compile_commands.jsonit's actually the first properly fast and robust C++ IDE I've ever used. You know if you've used a Java IDE the code intelligence just works and is fast and reliable. It's like that.