the clang errors Xcode gives you when using ObjC are generally quite helpful. They should be, as they represent decades of development effort (on GCC and then c

the clang errors Xcode gives you when using ObjC are generally quite helpful. They should be, as they represent decades of development effort (on GCC and then clang). Swift is notably less verbose, but mostly it's just as an ObjC dev you've developed years of experience and you know what that EXC_BAD_ACCESS probably means you forgot to do... with Swift you're a beginner again.