News for hackers. Stuff that matters.
Re:Visual Studio Code is designed to fracture by theptip on Monday September 30, 2024 @04:38AM (#41694875)
How does it stack up vs. CLion?
Re:Visual Studio Code is designed to fracture by eulgro on Monday September 30, 2024 @07:55AM (#41696158)
It doesn't, CLion is way better.
Re:Visual Studio Code is designed to fracture by tcbawo on Monday September 30, 2024 @08:16AM (#41696302)
What does it do better?
Re:Visual Studio Code is designed to fracture by okl on Monday September 30, 2024 @10:40AM (#41697658)
One problem I always had with VSCode, is that it seems to fill up its autocomplete suggestions with "near-string-matches" from files all over the project. The jetbrains tools are quite strict in that regard and won't propose random string matches that don't fit semantically.
Re:Visual Studio Code is designed to fracture by digitaltensor on Wednesday October 02, 2024 @01:07AM (#41717362)
That doesn't sound right. clangd should (and does) only suggest semantically valid suggestions. It's also much faster than the CLion's own C++ engine, though that might change with CLion Nova.
Re:Visual Studio Code is designed to fracture by chpatrick on Tuesday October 08, 2024 @04:46PM (#41781664)
I used CLion before I switched to clangd + vscode and it was orders of magnitude slower.
Re:Visual Studio Code is designed to fracture by chpatrick on Tuesday October 08, 2024 @04:46PM (#41781670)
CLion was what I used before and it was way clunkier than VSCode with clangd. Complicated libraries like CGAL just weren't usable for auto-complete, but were instant with clangd.