3 ms·
I suppose to each their own, but if anything except for the provisioning/plist stuff in Xcode is complicated to you, you must be used to something else because
by tomasien 13y ago
I suppose to each their own, but if anything except for the provisioning/plist stuff in Xcode is complicated to you, you must be used to something else because in and of itself xCode is phenomenal.
- pugz 13y agoxCode (sic) is far from phenomenal. I have been writing iOS apps since 2008 and Mac apps longer than that and Xcode has made significant progress, but is still mediocre. It's very telling that Jetbrains managed to pull AppCode out of nowhere and blitz Xcode. I had never before used an IntelliJ-based IDE, but within a week or two my productive increased severalfold. It really puts Apple's efforts to shame.
- eropple 13y agoI'm a big IntelliJ fan and I can't roll with AppCode. I admire the work, but XCode feels a lot better for native code development. (I do work in C++ and only use Objective-C for tooling via Obj-C++, though.)
- cageface 13y agoAppCode's C++ isn't quite there yet, I agree. Lately I'm also mostly using XCode because a huge chunk of my codebase is modern C++. But for pure Obj-C apps I'll take AppCode every day. There are so many little usability and productivity wins over Xcode.