Season one of Treme is finished, and I totally failed to produce the last two installments of the Treme essential reference. I think it’s because as the season drew to a close, the fictional plot points overwhelmed the factual depiction of New Orleans and its customs that so captivated me throughout the run of the series.
To fill in the gaps, I would recommend (as I did every week), Treme explained from the New Orleans Times-Picayune, and of course the ongoing series of interviews about Treme at A Blog Supreme.
Fans of the show will not want to miss David Simon’s interview with Alan Sepinwall, which includes a lot of exposition on what Simon intended with the show. Here’s what he had to say in response to complaints about the show being “too preachy”:
So I read Back of Town, and it tells me that we’ve not gone so far awry that the people who actually lost their homes, some of them are still exiled, all of them went through the torture of Katrina and its aftermath – the show is resonsant in its details. And that matters to me, in the same way it mattered to me that Marines found “Generation Kill” to be compelling in its depiction of modern warfare. And I don’t really care what Democrats or Republicans or politicians or people who were for the war or against the war thought about “Generation Kill.” I don’t care that somebody blogging in New York says when a character rants in New Orleans that they feel they’re being preached to.
Treme is, more than any other television series I can think of, a show made to be appreciated in this era. Here’s one of the questions Sepinwall asks Simon:
Just like you did on “The Wire” and “Generation Kill,” you threw people into the deep end of a culture they’re not that familiar with. Specifically with the Mardi Gras Indians, you clearly felt comfortable not having to even use the kid (Darius) for exposition. It was just, “We’re going to watch them work, we’re going to show them doing their thing. People will figure it out, or they won’t.”
Simon’s answer is interesting, but here’s my answer from a fan’s perspective. These days we have Google and Wikipedia to help us fill in the blanks. There are bloggers of all stripes writing about Treme. And of course the New Orleans Times-Picayune and NPR have been doing their part to fill fans in with all of the background information they can stand. So there’s no need for David Simon to fill in the blanks with boring explanations — fans who are interested have the Internet for that. It’s a show for the modern fan who’s willing to put in the effort to get the most they can out of television as a piece of literature. I appreciate they fact that they didn’t waste my time with stuff I could figure out on my own.
The state of the video tag
YouTube’s developer blog has a sort of state of the video tag post, explaining why the HTML5 approach works for experimental purposes but isn’t going to soon displace Flash as the default for their service. The problem of browser makers not agreeing on a single video standard to support is huge:
Just supporting one more format will roughly double the amount of storage they need for videos. (The exact amount will vary based on the effectiveness of the compression algorithm.)
Their full list of reasons why the video tag is not ready for prime time is worth reading, and it underscores a larger point with regard to standards as well. The bottom line is that it’s easier for Adobe to iterate on Flash than it is for browser makers to iterate on HTML. Adobe can add new features and push them out in an update that works in all of the popular browsers. And it seems like it’s easier to get people to update their Flash player than it is to get people to upgrade or switch from Internet Explorer. That’s what leaves us stuck on the least common denominator when it comes to implementing things with HTML. In other words, Flash isn’t going anywhere anytime soon.
My prediction is that the trend over the next few years will be Flash on the desktop and more robust HTML5 applications for mobile platforms, thanks to the lack of Flash on iOS and strong support for HTML5 on both iOS and Android.