Earlier quoted context omitted.
It's easier to blame than to admit running a service at Github's scale is highly complex and takes deep expertise.
It's also that many Rails shops have performance problems: which isn't the same as saying "Rails is slow"!!. "Getting performance problems at some point" is almost a rite of passage in Rails; I'm certain every rails developer has pored over N+1 queries, caching, async jobs, race-conditions, gems and whatnot to keep the system running. The only Rails projects that I worked on that never had performance problems are th…
You'll be hard pressed to find any stack that doesn't require this.