3 ms·

I don't think I'm making an extraordinary statement. If you look in their bug tracker, there are 500+ tickets with the term "freeze" in it. The reason is actual

by pnako 7y ago

I don't think I'm making an extraordinary statement. If you look in their bug tracker, there are 500+ tickets with the term "freeze" in it. The reason is actually known: being a Java IDE, the design takes for granted that many operations that are almost instant in the Java world can takes many seconds in the C++ world (meaning they'd need to put that in the background instead of blocking the GUI). Obviously there are (many) reasons for that. What you think is hairy might not be that hairy, in terms of parsing, to a compiler or static analyzer. If you're like most game developers, you use a simple subset of C++ that's C-like, which might explain why you're lucky. Maybe the word 'tiny' was excessive. It might not affect someone's homework, but in my case it definitely does have performance issues for my relatively small one-man projects. I'm not bashing the tool; I'm a paying user too. But no one can deny the many performance issues, and indeed the focus of the next major release is precisely to start addressing those.

cmrdporcupine 7y ago
The thing is that I've been using IntelliJ since version 3something, 15 years ago or so. It's _always_ had freezing problems. Over the years they made incremental progress on the Java front such that it became less common; or else workstations just caught up with the software. Or both. I also used AppCode extensively, that one actually behaved pretty well, overall. So I am not really surprised by CLion's performance/stability issues. I have a long love/hate type thing around this with Jetbrains. I hope they can get these things sorted out. I often wonder if they wouldn't be better rewriting in a non-GC'd language. Rust or something.
AnthonBerg 7y ago
My statement was inadvertently aggressive. I was attempting to be clear and logical but came out wrong. I am sorry :) It's a question of for-all-x vs. there-exists-x. I acknowledge that there exist x'es that are small projects that make CLion hang. I just wanted to make sure it was known that it's not all x'es. And that there exist y's that are large projects that don't hang. Cataclysm DDA is not a simple codebase :)

by pnako 7y ago

cmrdporcupine 7y ago

The thing is that I've been using IntelliJ since version 3something, 15 years ago or so. It's _always_ had freezing problems. Over the years they made incremental progress on the Java front such that it became less common; or else workstations just caught up with the software. Or both. I also used AppCode extensively, that one actually behaved pretty well, overall. So I am not really surprised by CLion's performance/stability issues. I have a long love/hate type thing around this with Jetbrains. I hope they can get these things sorted out. I often wonder if they wouldn't be better rewriting in a non-GC'd language. Rust or something.

AnthonBerg 7y ago

My statement was inadvertently aggressive. I was attempting to be clear and logical but came out wrong. I am sorry :) It's a question of for-all-x vs. there-exists-x. I acknowledge that there exist x'es that are small projects that make CLion hang. I just wanted to make sure it was known that it's not all x'es. And that there exist y's that are large projects that don't hang. Cataclysm DDA is not a simple codebase :)