News for hackers. Stuff that matters.
Re:CocoaPods announces Auth Server by al_gore on Wednesday May 21, 2014 @01:10PM (#7779386)
> Auto-updating rather than re-cloning and dragging files back into your project

That's the least usable way to do it, though. Use static library projects in submodules and a workspace/nested projects, and updated submodules will Just Work (unless there are breaking API changes, but Cocoapods can't help you there).

The main advantage of Cocoapods is shared dependencies. If you don't have those, it doesn't offer you much besides a non-git-native way to manage dependencies. Also, not having to manually edit your Xcode project to get the correct, single component path (instead of an absurd relative one) for a static library after changing to BUILT_PRODUCTS_DIR (why this has never been fixed, I have no idea).

Re:CocoaPods announces Auth Server by alloy on Wednesday May 21, 2014 @01:26PM (#7779467)
Yes, CocoaPods can’t fix API breaking changes, but as we use semantic-versions and encourage authors to follow those, it can at least be mitigated more easily. E.g. A version requirement of: ‘~> 1’ should then install the latest v1.x.x, but not v2 which has API breakage.

Obviously this is not fool-proof and many are still getting used to it.