3 ms·
Good for you, but at work I’m not so lucky (large C++ project == CLion is so slow to be only usable if you’re a zen master). For debugging, gdb -tui works for
by renox 6y ago
Good for you, but at work I’m not so lucky (large C++ project == CLion is so slow to be only usable if you’re a zen master).
For debugging, gdb -tui works for me (once I’ve learned to refresh the display after an output).
For coding, VSCode’s is much more responsive than CLion but its code navigation is inconsistent and it use >30GB of RAM once a week randomly (60 GB last week!).. I’m thinking about going back to Vim :-(
- xxpor 6y agoI've found clangd to be much more responsive than the built in LSP fwiw. No comment on memory though, my remote dev env has 384 gb so I don't really pay much attention :/
- ensiferum 6y agoInterested to know what is the size of the project? I'm currently working on something small about 60kloc of my code, another 60k in third_party and Qt5 as additional dep. There are a few hiccups every now and then when the Clion UI freezes for a few seconds but other than that it's been working really great.