CocoaPods downloads max out five GitHub server CPUs
1–10 of 320 posts
Re: CocoaPods downloads max out five GitHub server CPUs
#2Note how perfect that response from mhagger is. A clear, honest sounding assurance of what Github wants to deliver. A perfectly comprehensible description of what is the problem, and where it is coming from. And then suggestion how to fix it the project actually can work on, plus mentioning changes to git itself that Github is trying to make that would help. It not only shows great work going on behind the scenes (and if that is untrue, it at least gives me that impression, which is what counts), but also explains it in a great way.
Re: CocoaPods downloads max out five GitHub server CPUs
#3Wow, really impressive response from GitHub. The right amount of technical detail coupled with balanced tone--halfway between "we support you" and "you make us crazy."
One correction to the post title: it's not maxing five nodes, but five CPUs.
Re: CocoaPods downloads max out five GitHub server CPUs
#4Another reason I consider https://github.com/Carthage/Carthage a better solution of the dependency management problem.
Re: CocoaPods downloads max out five GitHub server CPUs
#5I love how this was like the perfect storm of things that could go wrong, and how it seems like mhagger is just amazed more than anything else.
Re: CocoaPods downloads max out five GitHub server CPUs
#6Another reason I consider https://github.com/Carthage/Carthage a better solution of the dependency management problem.
And https://github.com/apple/swift-package-manager once it's ready, which is similar to Carthage in structure (decentralized!).
Re: CocoaPods downloads max out five GitHub server CPUs
#7I love how this was like the perfect storm of things that could go wrong, and how it seems like mhagger is just amazed more than anything else.
Hardly. Do they hit edge cases? Yes! Is using GitHub for your CDN a dick move and going to cause problems, regardless? Yes!
The response from mhagger is unnecessarily apologetic, and I predict we'll see an official update from GitHub on this soon.
Re: CocoaPods downloads max out five GitHub server CPUs
#8Wow, really impressive response from GitHub. The right amount of technical detail coupled with balanced tone--halfway between "we support you" and "you make us crazy." One correction to the post title: it's not maxing five nodes, but five CPUs.
Yeah, 5 cpu's is an order of magnitude difference. ;)
Re: CocoaPods downloads max out five GitHub server CPUs
#9Note how perfect that response from mhagger is. A clear, honest sounding assurance of what Github wants to deliver. A perfectly comprehensible description of what is the problem, and where it is coming from. And then suggestion how to fix it the project actually can work on, plus mentioning changes to git itself that Github is trying to make that would help. It not only shows great work going on behind the scenes (an…
Yes, it's a hugely positive advertisement for the essential role that Github plays in the open source community. Also impressive is the followup message from a Github API developer (and Homebrew maintainer) offering access to a beta API that Homebrew is working with to reduce load. https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomm...
Re: CocoaPods downloads max out five GitHub server CPUs
#10I've always found Github's business model interesting. What if a massive open-source organization (e.g. Fedora, Apache) decided to use it for all of their development, integrating it with continuous builds and all the associated pulls. Of course this isn't likely to happen for a number of reasons, but there are large open source projects that could put a significant load on their infrastructure if they chose to use Github as their main code versioning system.