If someone has a magic rabbit / silver bullet, I’m willing to give it one last try, but I have my doubts. At one time I though of Jetbrains as innovators, and my "go-to" tool provider. This is not an isolated issue, and it is seriously tarnishing Jetbrains’ reputation. there are similar complaints about other Jetbrains products (IntelliJ, P圜harm, etc.) all over the web. If anyone from Jetbrains is listening, please pay attention. Something is seriously broken / wrong with the current state of affairs, and the trajectory that AppCode’s performance has followed. Tried tweaking JVM settings, allocating more RAM to the JVM, running AppCode off an external (2GBps SSD), etc. I've tried RAM disks for AppCode's cache / derived data. I’m not really looking for any suggestions at this point-I’ve tried everything from switching to the latest Java runtimes (via the Choose Runtime plugin), disabled every single plugin inside AppCode (including Git) in an attempt to “lighten the load”. I am trying to decide whether to cancel my subscription tonight or try “one more day”. I don't know what Jetbrains’ plans for AppCode are, but you guys *seriously* need to do something about the performance problems. Both the latest build, and the one before latest, are sl ll ooo oo ooo Completely unusable. Out of total desperation I tried the latest 2019.3 EAP builds. Yes, Xcode’s “inspections” aren't as “deep” as AppCode’s, and the lack of semantic highlighting in Xcode is a (somewhat bitter) loss. Xcode starts up rapidly (no more than 5 seconds to load my projects), and is usable right away. In total frustration, a few days ago I decided to switch back to Xcode 11.1 as my primary Swift IDE. Then, to add insult to injury, after the slightest tickle / code change, AppCode starts rebuilding indexes, module maps, etc. Symbol resolution has been become increasingly slow as the past 18 months have gone by. How can it not have built enough indexes to do everything really quickly. I mean, it's spent the past 5 minutes build indexes (on an iMac with 32GB RAM and 6 cores). I pop open AppCode wanting to do some work, and then wait up to 5 minutes while AppCode launches, indexes, updates symbols, seems to index some more, builds module maps, etc.Īfter all of the waiting, “indexing” and “pre-processing” I expect AppCode to resolve symbols almost instantly. The execution, however, has become increasingly abysmal (to me, at least, and for my use cases). Please contact us and we'll add another use to your code.I have used AppCode for the past 18 months or so, and think the “vision” for what AppCode could be is superb.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |