It's definitely not for every scenario. It will depend on your data, whether or not you need sorting as you mentioned, and how many total rows there are in the table (card effect becomes too much after 20 or so). However for this simple use case, we thought it the best way to go.
Yup, though the different way to do it with data- attributes and no content in the stylesheet was also written about here  in 2012, and demo'd here  at the bottom of the page in the "No more tables" example.
We've been using this same technique in several projects where it seemed appropriate for the past few years and have been loving it.
Yeah, I presumed I wasn't the first under the sun to do it; just thought it would be interesting to write about since some of my fellow front-enders hadn't seen the technique and google didn't turn up either of those links :)
TM took over back in the late 80's as the underdog because they made the great business decision to give venues a cut of the pie as opposed to charging venues for their services - which is what their competitors did at the time.
They quickly took demolished the competition and began setting up long term contracts, usually between 3 and 10 years with each venue.
Then, in 2010 they merged with LiveNation who owns a vast majority of some of the nations largest, most popular venues.
Major artists' managers and promoters all have close ties to TM/LiveNation as well, because it's where the money is. So when Taylor Swift goes on tour, these folks make sure they hit a TM venue at each stop along the way.
That's just the tip of the iceberg, but you get the gist.
"There is nothing which I dread so much as a division of the republic into two great parties, each arranged under its leader, and concerting measures in opposition to each other. This, in my humble apprehension, is to be dreaded as the greatest political evil under our Constitution."
That's just the thing - I don't think 'playing it safe' is the goal in Washington, or at least not the only one. As is, the goal for contractors is to stay on a project as long as possible, earning more money over a longer period of time. Waterfall is a perfect excuse to do just that.
I agree that's an issue, but I was thinking more of the decisions of the people who hire the contractors. The right Agile approach to a project is to structure it as a series of small wins and losses, rather than rolling the bones on one big win/loss. It's my hope that calculus will appeal to career-minded officials, especially since the Agile approach lets you demonstrate value earlier (thus reducing drama), lets you bet more on your wins, and dramatically reduces the chances of large failures.
'Playing it safe' is also the goal of the gov't civilian managers of those projects- they have a promotion schedule to hit and having a 'failure' on their resume jeopardizes that. And since they're only going to be there 2-3 years, the goal is just to keep things propped up until they rotate out.
Unfortunately, you are in the vast minority of people, probably even on hacker news (I would guess less that 1% of overall population ).
So the decision has to be made, just like whether you want to support IE7 users, whether or not you want to put in the extra time to support those edge cases.
And as always, it depends on the type of site you are running. If it's Amazon, that 1% matters a shit ton. If it's a side project or SaaS startup for example, it makes sense to hold off on supporting those 1% in favor of more pressing features.
I think this is a legitimate question. Personally, it would be cool to scan lists of API's for idea inspiration but this doesn't really provide that functionality. Now what would be cool here, is if the APIs returned here had docs presented on the website with a consistent UX/UI. But then you would need an API for an API :)