Thursday, January 31, 2008
Jerry Springer - The Opera
Jesus is portrayed in a diaper debating the Devil, with Springer as referee.
The Ku Klux Klan surprises us, swishing their gowns in an energetic chorus line.
The KKK sings and dances for the JerryCam.
Jerry and guests with big hair go hand in hand.
Jerry's chorus is anything but Greek.
The "real" Jerry has real guards recruited from the Chicago Police Department.
Jerry has strange guests on the Operatic version of his show.
Opera is not a dead art. Far from it. But it has been a long time since a new opera had protesters picketing performances, especially in the less fundamentalist U.K. Because the content of Jerry Springer - The Opera includes the characters of Jesus and the Devil depicted in less than worshipful words and images, it has raised a howl of outrage, one heard even in the USA where its scheduled Broadway run was cancelled due to skittish backers. American audiences, they think, are far too conservative for this.
Perhaps the spectacle of a tap dancing Ku Klux Klan sent a few too many chills down their spine and into their pocketbooks. Yet it seems that this opera has sold out its run wherever it has played. In 2007 several regional companies mounted productions, taking enormous risks with their resources and supporters, but weathering the storm, and in once case, extending the run by a month.
Recently, it played two nights at Carnegie Hall in a production where Harvey Keitel played the non-singing role of Jerry Springer. Of course it was sold out, and received rave notices from the New York Times, which does not compliment new works easily.
Many excerpts of the opera are available on YouTube since the entire production was televised on the BBC. On January 7 2005, the day before the broadcast, the BBC announced that it had received over 47,000 complaints about its plans to screen the opera � the most complaints ever received about a British television broadcast.
Many commentators, including the BBC, attributed such a high volume of complaints to an orchestrated campaign by various Christian groups. Supporters of the BBC's broadcasting of the show pointed out that the supposedly blasphemous content was clearly presented as a fantasy in the mind of the dying central character and was not intended to be a serious comment on Christ or Christian theology. John Beyer, chairman of Mediawatch-UK, argued that the BBC should shoulder much of the blame for the campaign against the opera since they had promoted the opera as "pushing back the boundaries of taste" and "controversial" when it had never been intended to offend the groups who campaigned against it.
In the past year there have been five productions of the opera in the USA. The two concert presentations this week at Carnegie Hall, plus full productions at Chicago's Baliwick Repertory Theatre, Minneapolis Music Theater and Playhouse on the Square in Memphis. The Chicago production ran with extensions, for three months, selling virtually every ticket it could print.
Upcoming are productions in February at Stage West in Des Moines, and in midsummer at Studio Theatre's Secondstage in Washington, D.C., a production I hope to see and report on both here and for the web magazines Maverick Arts and Berkshire Fine Arts.
Christians express their distress over the opera's content, ignoring its ultimate moral message.
One of the reasons Christians get upset at the opera is its use of profanity. "It has been accused of including "8,000 obscenities"�it is not known where this count originated, but the 8000 figure is popularly quoted. This however is impossible, as 8000 obscenities over the show's 120 minute runtime would mean that there were 66 obscenities a minute, and thus 1 and a half a second. Several publications, including the Daily Mail and The Sun, claimed a figure of "3,168 mentions of the word fuck and 297 of the word cunt".
As stated in the BBC's findings, however, "the reported figure was in fact a vast exaggeration. In reality, there were 96 uses of "fuck" and nine uses of "cunt". While a substantial number, this was not necessarily unacceptable in terms of late night terrestrial television." The numbers resported were found by multiplying the number of cast members singing a profanity at the same time, ie the reported 297 uses of the word cunt is the result of multiplying the 33 cast members with the genuine amount of uses of the word, ie, nine times.
According to director Stewart Lee, there are 174 swear words in all." From here:
http://www.answers.com/topic/jerry-springer-the-opera-1
There is a DVD of the opera, though since it was issued in the UK I am not sure if it will play on all US machines. Other than the YouTube excerpts I am not aware of any music excerpts being available. Anyone can use the comments section to add resources, and I will make updates on additional productions through comments as well.
This is a work well worth seeking out, for blessed are the singing, pole-dancing fetishists. As Ben Brantly wrote in the New York Times:
Those who attended �Jerry Springer,� which stars an affectingly disaffected Harvey Keitel in the nonsinging title role, expecting to snigger and hoot were not disappointed. There�s a guaranteed off-the-charts camp quotient in a show that sets the televised confessions of pole-dancing housewives and men with diaper fixations to music that often leans more toward Bach than Broadway.
In terms of sheer audacity, �Jerry Springer� is a helluva lot funnier than, say, �Young Frankenstein.� This is, after all, a work that features numbers with mock-liturgical titles like �Jerry Eleison.� And though I�d love to say that the demonstrators who assembled outside the theater on Tuesday to protest a show that �blasphemes our Lord� would be disarmed if they ever got to see �Jerry Springer,� I can�t.
Monday, January 28, 2008
Deadline Extension for the Android Developer Challenge
We'd like to let you know that we are extending the submission deadline for the first Android Developers Challenge to 14 April 2008. Based on the great feedback you've given us, we've made significant updates to the SDK that we'll be releasing in several weeks. In order to give you extra time to take advantage of these forthcoming UI and API enhancements, we've decided to extend the submission deadline. In addition, a fair number of developers have also asked for more time to build and polish their applications.
Of course, you can stay the course and submit your applications using any version of the SDK that you'd like. We're looking forward to seeing some great apps, especially after we've had a chance to incorporate some of your feedback into the Android platform.
Here is the updated time line:
14 April 2008: | Deadline to submit applications for judging |
5 May 2008: | Announcement of the 50 first round winners, who will be eligible for the final round |
30 June 2008: | Deadline for the 50 winners of the first round to submit for the final round |
21 July 2008: | Announcement of the grand prize winner and runner-up |
For additional details on the Android Developer Challenge, please visit the ADC page.
Good luck and good coding!
Tuesday, January 22, 2008
Intercontinental Androids
When I recently blogged about our upcoming Android Campfire, I hinted at some international events we've been working on. We've now finalized plans on those, and registration is open.
We've got Android Code Days lined up for these locations:
- On 31 January, we'll split up, and host Android Code Days in London, UK and Tel Aviv, Israel.
- On 23 February, we'll host one in Boston, Massachusetts. (We'll post the registration page for this event soon.)
In addition, as we've announced via Mobile Monday Germany, we'll be having a similar event in Munich, Germany on 29 January.
What's a Code Day, you ask? Well, it's just our name for a day-long introduction and immersion session for Android. We'll give a technical introduction to the platform as well as a more in-depth look into topics of interest to the attendees. Then we'll have a free-for-all coding session that we like to call the "Laptop Lounge".
In other words, the agenda is largely up to you! Each of these events includes food and refreshments and is free of charge, but space is limited so please be sure to click on the registration links above to reserve your spot.
I said before that I think I have a really cool job; now I get to travel the world to meet developers and talk about cool technologies. I can't believe I get paid for this!
Friday, January 18, 2008
You can't rush perfection, but now you can file bugs against it
We expected a lot of attention when we launched the early look of the Android SDK, and that's certainly what we got! Developers haven't been shy in speaking their minds on our Discussion Groups, and we've been listening. We've also been hard at work on Android, and meanwhile the Developer Challenge has been heating up and the submissions have started coming in.
We've been improving that "early look" and are preparing for the next big SDK release, so it's time to take the whole thing up a notch. As we move toward the first handsets, it's time to formalize the process, and the first step in that is to enable an issue tracker for developers to submit feedback.
I know a great many developers have been waiting eagerly for this, so I'm very pleased to be able to say that the Issue Tracker on the Android project on Google Code Project Hosting is now open for business. You can find the Issue Tracker here:
http://code.google.com/p/android/issues/list
We're now actively tracking that system, and we invite developers to file an issue to let us know about any problems you find with the SDK.
When you submit an issue, remember that the more detail you can give, the more likely the issue is to be addressed. (We especially enjoy the subtle and delicious flavors of reproducible sample code.) Of course, you'll still be able to ask for answers and advice on the Discussion Groups, so don't stop posting there. We'll be reviewing submitted issues regularly and keeping the database up to date, so that you can rely on it as a reliable and timely resource.
I think just about everyone will find this useful -- I know I definitely will. Happy coding, and now: happy reporting!
Tuesday, January 15, 2008
Black Rice Dessert
Ingredients:
240 g Black glutinous rice
(washed & drained)
60 g White glutinous rice (pulut)
(washed & drained)
7 c Water
2 Pandan leaves, knotted
1/2 c Sugar
Pinch of salt
1/2 T Tapioca flour or cornflour
Combined with 2 Tbs water to
Form a paste
1/2 c Thick cocnut milk
Pinch of salt
Directions:
Put rice in pot with water and pandan leaves and bring to a boil. Reduce heat to low, remove pandan leaves and simmer for 45 minutes until liquid is thick. Add sugar and simmer for 10 minutes. Add salt and thickening. Remove from heat.
Serve in small bowls topped with 1-2 tablespoons thick cocnut milk.
Monday, January 14, 2008
Who wants cocoa & s'mores?
It's been a busy few months. First we announced Android, then we released an early look of the Android SDK, and just last week we started accepting submissions for the Android Developer Challenge. Now that we've got things moving along, it's time to stop and smell the roses.
Our developers will be a huge part of Android's success, so we want to meet you, our colleagues. We're working on some events around the world that we hope to announce soon, but to kick things off, on the 23rd of January we'll be holding a Campfire about Android.
Join us for food, drinks, and great conversation! Come meet other developers as well as Googlers working on Android. Talk business, talk pleasure, or just hang out – it's up to you.
We'd love to see all of you there, but unfortunately space is limited. We've set up a registration page for you to sign up, so head on over and reserve your spot!
Tuesday, January 8, 2008
Quick 'N Easy Cooking Sardines
1 tin Sardine ABC
1 ea. Ripe Tomato,sliced
2 ea. Red Chili, sliced
5 ea. Shallots, sliced
2 ea. Garlic, chopped
2 ea. Lemon Leaves or Lemon Grass
As needed Cooking Oil
Salt and pepper to taste
Cooking Method:
Separate sardines from its juices. After dry, fry sardines to get more flavor, don't over cooked but fry about 2-3 minutes. Take some oil in pan to saute garlic, shallot and chili and lemon leaves. After aroma comes out, add tomato and juice, cook fro some time than finally add fried sardine and continue cooking for additional 5 minutes, adjust seasoning. Remove from heat and serve. Garnish with fried shallot and green onion if you like.
Cooking sardines is very simple way of cooking, you don't even need additional spices or herbs. Just heat up in pan or putting it in microwave. But to you who like more flavor, its good to cook as recipe above. Eggs can be added while cooking if you like.
Thursday, January 3, 2008
Rising to the Challenge
I think I have a really cool job, because I get to do a little bit of all those other cool jobs that you wish you could have. Today, I get to be like the Chairman from Iron Chef.
If you've never seen the show, the premise is that a slightly mysterious and rather eccentric guy known as the Chairman fulfilled his dream of presiding over a huge, extravagant cooking tournament. In a similar vein, today I get to make the announcement that the Android Developer Challenge is now "open for business" and accepting your submissions. The excitement! The anticipation! The pageantry!
Okay, not so much pageantry. But I do think it's pretty exciting, and I can't wait to see what you developers will come up with. Some of you have already given us a little taste of the cool stuff you're working on, and I'm eager to see what everyone else is cooking up.
To submit your application for the Challenge, click here to go to the Submission Page. Once there, you'll pick from one of three versions of the form based on whether you're working alone, in a team, or for an organized company. We've tried to keep things simple, so all you have to do is choose the form that applies to you, fill it out, attach the .apk file for your application, and you're done.
You also have the opportunity to upload a file containing documentation about your application. Any readable format is okay, although we prefer PDF or plain text. This file can contain anything that you think is important. For instance, you might include instructions on how to use your program, a design document that describes the next steps you plan to take, or a narrative that explains the vision of your application. We do ask that you submit your documentation and application in English, so that all the judges (who will be chosen by members of the Open Handset Alliance) can easily read it.
It's also very important to look at the Terms and Conditions. These are the rules for the Challenge and describe what you need to do to participate. Read them carefully!
The submission period is open until March 3, 2008, so you don't need to rush to submit your application just yet. March 3 is definitely a hard deadline though, so you must have your applications submitted by then. If you choose to submit now, you can always re-submit a later version of your application closer to the end. (I'd bet the participants on Iron Chef would love to be able to refine and re-submit their works to the judges.)
Maybe it's no Kitchen Stadium, but I still think we're in for a lot of fun. I hope everyone is having a great time developing for Android, and I hope to soon see the fruits of your labor. Good luck, and happy coding!