tag:blogger.com,1999:blog-7971303847554312963.post3089356890709016777..comments2019-05-24T03:26:48.986+03:00Comments on iOS and OS X Development: 9 Reasons to try AppCode for Objective-C codingVadim Shpakovskihttp://www.blogger.com/profile/07971682033974005558noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7971303847554312963.post-71189148416050812662015-04-10T18:40:48.662+03:002015-04-10T18:40:48.662+03:00Worked in Appcode for quite a while. Frankly I got...Worked in Appcode for quite a while. Frankly I got tired of filing bug reports to them. It shares a handy code editor with other JetBrains products, but that&#39;s all. The rest has an awful user experience. Debugging is not handy, editing PLISTs and project props is not handy, working with XIBs and storyboards is virtually impossible. I don&#39;t even understand why they created that half-assed editors. Refactorings? Most of the time it&#39;s more powerful than Xcode, but it also does mistakes renaming inappropriate entities. At some point I found it tiresome to switch between editors, so I just do all my job in Xcode again and run Appcode occasionally to organize imports. Actually even this refactoring is disappointing, since it doesn&#39;t sort imports alphabetically. I don&#39;t think it will ever become a dominant IDE for OS X/iOS development.Aliaksei Nestserauhttps://www.blogger.com/profile/00775859089023880802noreply@blogger.com