Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use CocoaPods in example project #58

Merged
merged 2 commits into from Jun 13, 2016
Merged

Conversation

pcantrell
Copy link
Member

Switching the example project from Carthage to CocoaPods. Reasons:

  • Despite its initial promise, Carthage adoption is low — and now looks like it will remain permanently low with SwiftPM coming. Far more users interesting in trying an example project will have CocoaPods installed.
  • Carthage has proven inflexible, slow, difficult for new users to set up, and reluctant to adapt to user needs. CocoaPods is a terrifying behemoth, but one that works well.
  • CocoaPods makes it easy to test Siesta changes locally in the example project, because it supports local file system dependencies. Carthage does not, and thus requires a push or hackery to test changes. (This shortcoming also forces a redundant checkout with Carthage.)
  • This should make pod try work properly.

This is for the GithubBrowser example project only. The core Siesta project will continue to use Carthage for the time being.

Objections? Speak now!

@onekiloparsec
Copy link
Contributor

I had so many nightmares with the Behemoth, as you say, I still prefer the simplicity and distributed philosophy of Carthage. But to give a try, CocoaPods has certainly a larger userbase.

@pcantrell pcantrell force-pushed the use-cocoapods-in-example-project branch from 029a2ce to 516e815 Compare June 12, 2016 19:30
@pcantrell pcantrell merged commit 88fea7e into master Jun 13, 2016
@pcantrell pcantrell deleted the use-cocoapods-in-example-project branch June 13, 2016 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants