Disappointed AppCode 2.0 has been released in its current state

I am a fan of the Jetbrains IDE lines, and have been a propoent of AppCode within my company.  When I saw 2.0 was out, i upgraded right away.

Its been a pretty miserable experience.  The IDE freezes all the time doing simple tasks.  I think they are largely related to OC-3286 but I have encountered other cases where the IDE freezes for a good 5-20 seconds.  Not sure how bugs are being prioritized, but this one has been reported for 12 months and has a ton more votes than anything else I see.

At this point I would caution anyone considering upgrading to do a trial before buying.  I am warning my team to stay away until it works properly.

5 comments

I've gone through all the EAPs and I installed the final yesterday and I'm happy with it.  I think they have done an awesome job and even if there was a 1 minute countdown timer every 5 minutes I would still be more productive than in XCode.   My dev environment is a Macbook Air Core2Duo with 4GB of memory and I don't have many stalls, mainly just when I externally alter the project.

My only gripe which I don't know if it's user configurable is when using the Darcula theme I have a hard time discerning which tab is currently selected.  I looked for a config setting to set a certain color for the currently selected tab but didn't find anything.  

0

My gripe is that it doesnt offer any features in 2.0 that are a big enough upgrade over 1.6 to overlook that fack that its slow and buggy.  Constant freeze ups really highlights that no one at Jetbrains uses this IDE on a regular basis.  Its really just intolerable for someone trying to increase productivity, which is the whole point of using AppCode over Xcode.

I would be super pissed about this if I had paid to upgrade (my license purchase was in the free upgrade window).  So I am cautioning anyone else considering an upgrade, make sure you use a free trial for a while before paying to upgrade to beta software.

I have downgraded back to 1.6.  Hopefully they will get the next point release right.

0

diademlee wrote:

  Constant freeze ups really highlights that no one at Jetbrains uses this IDE on a regular basis.  


No it doesn't. At most it shows that they can't reproduce this on their own machines, and either haven't received enough data from those who do suffer from the problem, or the data's inconclusive.

Case in point, me. I use AppCode 2.0 "on a regular basis" (ie. full-time), running on an old (late 2007) macbook, a slow machine by current standards, and am not suffering the performance problems you talk about (though I did in the earlier EAPs). I do get some drastic slowdowns when editing precompiled headers on some projects, but other than that, AppCode is pretty swift in use for me (albeit very resource hungry).

0

crispinb wrote:

No it doesn't. At most it shows that they can't reproduce this on their own machines, and either haven't received enough data from those who do suffer from the problem, or the data's inconclusive.


The PCH issue is one of the most commented and upvoted bugs.  Its been reported for 12 months in one case.  Its reported multiple times with git repositories of code that reproduce it.  I hardly think that qualifies for any of these excuses.

I have a 6 month old MBP (solid state drive and all that jazz) and I still had consistent issues.  I spoke with 2 developers on another team here recently, working on a differnt project and codebase, they suffered the same issues when using 2.0.

I am glad it works without issue for you.  It doesn't for me and others I have talked to.

0

@Jobe: I guess I'm just suggesting you tone down the rhetoric a bit. I can understand the desire to rant at companies that just won't communicate (there are too many of those!), but Jetbrains is one of the most communicative companies I've ever bought software from.

I'm not in the slightest doubting that AppCode 2 is causing you problems, nor that it's JetBrains' responsibility to work on fixing them.

0

Please sign in to leave a comment.