<story><title>CocoaPods downloads max out five GitHub server CPUs</title><url>https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935</url></story><parent_chain><item><author>manyxcxi</author><text>I was astonished at how selfish&amp;#x2F;myopic&amp;#x2F;whatever alloy&amp;#x27;s response was.&lt;p&gt;To be blunt, you&amp;#x27;re abusing the shit out of SOMEONE ELSE&amp;#x27;S product that you&amp;#x27;re not even paying for. Your first question shouldn&amp;#x27;t be to see what Github can do for you to make it so you don&amp;#x27;t have to make changes. You should be falling over yourself investigating all available avenues for reducing load.&lt;p&gt;It&amp;#x27;s an incredibly entitled way to think about things and I would have a real hard time employing someone who&amp;#x27;s first response was like this.</text></item><item><author>onli</author><text>Note 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.</text></item></parent_chain><comment><author>tptacek</author><text>I don&amp;#x27;t know, it sounded to me like he just didn&amp;#x27;t totally understand what Github was saying. By the end of the thread, it seemed like everyone was agreeing. I wouldn&amp;#x27;t be comfortable using words like &amp;quot;selfish&amp;quot; to describe any of what I read.&lt;p&gt;I certainly don&amp;#x27;t think the barb about your willingness to employ people who write things on Github issues threads that you disagree with is helping anyone understand any part of this situation. I understand the urge to find ways to be emphatic about how much you disagree with things, and I &lt;i&gt;often&lt;/i&gt; find myself compelled to write lines like that, but I think they&amp;#x27;re virtually always a bad idea.</text></comment>
<story><title>CocoaPods downloads max out five GitHub server CPUs</title><url>https://github.com/CocoaPods/CocoaPods/issues/4989#issuecomment-193772935</url></story><parent_chain><item><author>manyxcxi</author><text>I was astonished at how selfish&amp;#x2F;myopic&amp;#x2F;whatever alloy&amp;#x27;s response was.&lt;p&gt;To be blunt, you&amp;#x27;re abusing the shit out of SOMEONE ELSE&amp;#x27;S product that you&amp;#x27;re not even paying for. Your first question shouldn&amp;#x27;t be to see what Github can do for you to make it so you don&amp;#x27;t have to make changes. You should be falling over yourself investigating all available avenues for reducing load.&lt;p&gt;It&amp;#x27;s an incredibly entitled way to think about things and I would have a real hard time employing someone who&amp;#x27;s first response was like this.</text></item><item><author>onli</author><text>Note 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.</text></item></parent_chain><comment><author>BogusIKnow</author><text>I had the same impression from alloy&amp;#x27;s response. I&amp;#x27;ve basically read it as &amp;quot;hi ho we will not change anything&amp;quot;.&lt;p&gt;And it had this passive agressive ring to it, with the hand clapping and the hurray in the beginning and the stone walling in effect.</text></comment>