745 karma · joined March 5, 2009
What happens when your 300MB deploy needs to be pushed from your development machine out to 15 different production servers? I wouldn't want to send ~4.3GB for every deployment. Furthermore, a quick deployment time is valuable when a crucial fix needs to be pushed to production.
This is not to mention the space that your 300MB deploy is going to take up on the hard drives of your production machines if you deploy twice a day. That's over 213GB a year per machine, sounds like you would need to start deleting old revisions. Or start just sending the diffs.
Another point to note is that there is an incentive for all of the Y-combinator startups to say they had a good experience, because if they said otherwise they might be burning the bridges they built (which they would not want to do, even if those bridges are not worth what YC charges for them).