Re: iOS/RestKit/XCode 4.6
Re: iOS/RestKit/XCode 4.6
- Subject: Re: iOS/RestKit/XCode 4.6
- From: Jens Alfke <email@hidden>
- Date: Wed, 20 Feb 2013 20:03:24 -0800
In general I've found that anything this difficult to just add to a project is probably not worth adding in the first place.
As the author of a number of Cocoa-based libraries, I disagree. In many cases the problem is that Xcode doesn’t have good support for integrating 3rd party code into a project. It’s gotten a little bit better over time, but all too often you still have to mess with build settings like search paths and build phases.
People seem enthused about CocoaPods lately, and it sounds like they fix some issues, but they introduce the major problem that my library’s code is now entirely dependent on your target’s build settings (like prefix headers, compiler modes, warning flags…) As far as I’m concerned, that’s just as big a mess. I mean if the developers were so lazy/incompetent that that couldn't be bothered to write decent up to date instructions on how to install it then what chance does the code itself have? It’s not “couldn’t be bothered to write”, it’s “couldn't keep the instructions up to date every time something changes in Xcode”. I’m definitely guilty of that in some of my libraries :-/
I’ve also found that the ability to write great code, and the ability to write clear docs and set up clean packaging, are not necessarily correlated. Ideally everyone would have both skills, or all projects would be team-ups by people who can contribute their skill, but it’s not always the case.
—Jens |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden