Clion IDE

I never do this, but this is exceptional.  

 

I have come across a lot of IDE's and development tools in my 20 years of development but this one takes the biscuit. This product couldn't be farther from production ready. It is just so fundamentally broken from the top down, inside out, every which way. This post will hopefully save some other poor developer from the same time loss I just incurred. 

 

1) The debugger systematically times out. I changed xserver over to exceed having heard that mentioned by somebody as a solution. No improvement. Debugger unusable. 

2) The editor just cannot handle it. The most basic changes in the source causes the indexer to go nuts under the covers. It ultimately hangs, giving up, starting again, giving up, restarting. The IDE is blocked most of the time and I'm sitting there like a tulip waiting for control to be given back to me.  Editor unusable when refactoring/moving code/changing code. 

3) Even the shortcut keys to find in file mess up when you type too fast... the word/string you're looking for gets inserted into the source file. Editor flaky.

4) The console window is just so unbelievably slow it should be shut down/removed immediately. console window flaky.

5) Unless I have read wrong, the output of build has to go into a Clion "Debug" directory, which doesn't suit me at all. I ended up having a clion build and a "real" build side by side. Thats just wrong. Build possibly flaky.

 

The marketing is brilliant. The video/demo is brilliant. The svn integration is excellent. The rest.... bin it! Why not put it back into serious development and release a "working" version in 6 months. You have a wonderful opportunity to get into the market where eclipse/kdevelop even xcode and visual studio (though try beat their debugger and I WILL pay money) have a very strong foothold. You are blowing it. It simply isn't production ready. If it did what was advertised it could be awesome.

 

There is no way in earth I would ever every conceive of paying money for this "tool". Make it do what it says on the tin and I would consider re-evaluating it. For info, I have ALWAYS coded in an IDE (including codeblocks where eclipse wasn't available on Linux). I always had a bit of teething problems but always managed to get the IDE's debugger (gdb ultimately) working. It cost me a day or two fiddling but it always worked. I've wasted more than a week on this and its time down the toilet. I have spent the last two days using gdb with -tui option, installing and running vim over ctags with a few svn scripts from colleagues.... I'm up and running. I don't think I'll go back to an IDE (well maybe xcode on mac or visual studio on windows as they are really good products). 

 

Sorry to rant like this but its not frustrating, its vexing. There are surely a team of gifted java developers working behind the scenes on that product but something, somewhere (someone!) along the Clion development food chain needs to take a look at how they are doing their job and consider the extensive negative feedback you can find on Clion via google. The marketing team can keep their jobs BTW, they are excellent :) 

 

Anyways, sorry to be so negative but its an honest opinion from somebody thats been around more than a year or two and wanted the IDE to work.

 

An no, I'm not opening support tickets :) 

 

Good luck. 

 

 

6 comments
Comment actions Permalink

Hi,

First of all, we are sincerely sorry you feel this way.

Second, I would suggest to go through the list of your problems step by step to find out the source of them, since it's not all typical problems for our users (the only I could see is a debugger timed out, but we've are currently working on it in the latest EAP and really need some additional info from those who are still experiencing this). However, some points could be a misunderstanding of how CLion works and which features are available (for example, to control the build output directory).

We are for sure aware of some bugs and problems and currently are working on them, thus some additional information from your side will be really helpful. Especially to solve your problems in particular.

If you feel, you are ready to communicate further, please, submit a support request and we'll go through it step by step - we'll try to help you for sure.

Regards,

0
Comment actions Permalink

I want to chime in on this - I actually LOVE CLion and I'm very excited about the future for it.  However, the performance issues are very real, and I'm concerned that JetBrains doesn't have a plan to address them.  It seems there are two fundamental issues:

1.  Indexing / parsing / analyzing just takes too long.  I know that C++ is notoriously difficult to parse.  Honestly, I haven't seen any other IDE get this right either.  But what I don't understand is why CLion seems to spend so much time reparsing files that haven't changed.  Simply adding a variable to one header file can cause minutes of re-indexing.  There needs to more effort put into the internal index and how to update it much more cheaply.  For all of the warts of C++, I don't see any fundamental reason that you can't maintain an internal structure that is as performant as whatever you do for Java (which is awesome!).

2.  The separation between the AWT event thread and the 'worker' threads is not managed correctly.  I stopped to type this now because I've been waiting for 6 minutes for the CLion UI to become responsive again.  This was kicked off by changing a single line of code in one cpp file.  I've documented this problem in: https://youtrack.jetbrains.com/issue/CPP-5609

I hope JetBrains can make a public commitment to address these issues.  It's really disheartening to see bloat features like Python support being talked about instead of making the core product work.  I think you guys have great potential to completely own the C++ IDE market but you have to focus on the basics first.

0
Comment actions Permalink

Matt,

Thanks you very much for the feedback and for the report. We really appreciate it.

We keep working on the indexing/parsing performance continuously, together with the new features. Incremental parsing is implemented, but for sure there is a place for enhancements. We are working on them.

We'd like just to remind, that CPU snapshots (https://intellij-support.jetbrains.com/hc/en-us/articles/207241235-Reporting-performance-problems) and project samples where you feel the performance is bad is really helpful for us.

Regards,

 

0
Comment actions Permalink

I agree with Matt in every point. You should focus on the basics first. Performance is horrible. I experienced every problem Matt said.

0
Comment actions Permalink

I just installed the 1.5 EAP from Feb 3rd and I'm happy to report that performance is GREATLY improved for me.  I think there's still more work to be done in the performance of the analyzer but the issues with the entire GUI locking up are almost non-existent.  Nice work to the CLion devs!  I'm looking forward to seeing continued improvements.

0
Comment actions Permalink

Thanks, we'll continue working on the performance.

0

Please sign in to leave a comment.