CLion uses ~1+ GB of memory for a simple Hello World project. Haven't even tested a complex program yet.
CLion is slightly sluggish. Clicking tends to not be the usual snappiness one expects from other IDEs (CodeLite, QtCreator, even VS). It's the typical experience I've encountered from Java apps over the course of 15+ years now, which, consequently, make me avoid them like the plague (other reasons to avoid Oracle notwithstanding). I figured I'd give this one a shot. Maybe things have improved, but maybe not?
Using 1-2 GB memory might not bother if it was to ensure being incredibly fast, responsive, and stable (as is the case with Chrome, for example). But it's already crashed after a [Run] once, with a short bit of typing lost despite autosaves. I like the autosaves by default but I dislike not being able to truly know/see if a file is saved or not (e.g. filename.cpp* vs. filename.cpp).
[Bug]? I noticed no default keys for creating a new file (how odd). I went to the keymap, added one for New File using an empty combination (i.e. ctrl+\ ). That didn't work. Tried adding it with another blank (i.e. F10). Didn't work. Instead it triggered the [File] menu.
[Bug]? When running a program that's asking for input, the cursor: 1. doesn't align and blink at the end, instead it's over to the left of the line. 2. When it's a blank line (e.g. cin.get()), no blinking cursor is shown.
I'd like the optoin to run the program in a typical pop-up console like other IDEs do it. Maybe it's an option and I didn't notice. Or maybe I wouldn't care if the built-in one was better/speedier.
- CLion has appeal. I like parts of it. I'm glad it's another massive IDE option now, especially for those who find it working well.
Tested on Win7-64, 8 GB. I might try Debian later.
What's it like for others here?
Is this usual or will performance drastically improve for a release?