Pretty inspiring to a language designer, and a great example of information design for everyone else.
Yet another test of blogging features … if you want to see the original site, check out:
More news as it happens.
Somewhere in an alternative universe, there is a version of Star Wars: Episode I: The Phantom Menace starring Haley Joel Osment as Anakin and Robin Williams as Jar Jar.
And it rocks.
In that universe, George Lucas broke his hip just before filming began and handed the directorial task to his good friend Steven Spielberg. Busy with his own projects, Spielberg hired M. Night Shalayman to smooth out some problems in the script, and Shalayman in turn introduced Spielberg to Osment, starting a collaboration that would later continue in Spielberg’s critically acclaimed movies Artificial Intelligence in 2001 and Harry Potter in 2003.
The real turning point in the production was the hiring of Robin Williams to replace Ahmed Best as Jar Jar Binks. Spielberg was reluctant to replace another of Lucas’ chosen cast but after repeated attempts to tone down the character, Best’s creative differences with Spielberg reached the breaking point and he quit the production. Almost simultaneously, Lucas suggested Williams to Spielberg for some role after seeing him perform at a charity fundraiser at Skywalker Ranch, and Williams heartily agreed.
The completed film was two and a half hours long and made over seven hundred million dollars in its domestic release. Lucas, Spielberg and Williams threw their marketing weight and star power behind the film, but it was Olsment’s Oscar-winning portrayal of Anakin Skywalker that generated real audience buzz. Fleshing out a role already greatly expanded by Shalayman, Olsment brought quiet dignity and heartrending pain to the boy who would be Vader, and became the youngest winner of the Oscar for Best Actor.
While Star Wars: Episode I: The Phantom Menace would go on to win nine academy awards, the biggest upset of Oscar night was Robin Williams’ shutout for his portrayal of Jar Jar Binks. Acting largely from an improvised script, Williams brought both gravity and humor to the role of the exiled Gungan warrior — providing a much-needed element of comedy in Spielberg’s often grave treatment of the fall of Naboo — and later proved the perfect foil for Olsment’s tortured Anakin in his moving death scene at the hands of Darth Maul. However, since the physical appearance of Williams’ character was computer generated, he was technically shut out of the category of Best Supporting Actor, despite the extensive write-in campaign on the part of the Academy voters.
After recuperating, Lucas returned to the executive producer role on the Star Wars saga. Despite his injury, he had remained intimately involved with the production of the movie and was pleased with the final outcome, despite his initial resistance to changes made by Spielberg and Shalayman. Shalayman and Spielberg both attempted to bow out of the saga, reluctant to continue without the magic of Williams nor Olsment, who could not realistically return in later sequels. However, after intense personal lobbying Lucas convinced both Shalayman and Spielberg to return to the project, and work on the sequels began in earnest.
Episodes II and III are being filmed back to back in Tunisia and England as we speak. However, despite the critical buzz already being generated about the project and the remarkable collaboration of the three directors, there is little doubt that the Star Wars creative team will be hard pressed to top Jar Jar’s poignant death scene in Anakin’s arms. As Obi-Wan Kenobi and Qui-Gon Jinn watched helplessly on, young Skywalker is first touched by death as Jar Jar utters words that echo later in the series:
“Remember, Ani. Inna Force, I be with you always.”
Interestingly, Van Allen (of the Van Allen Belt fame) now questions human spaceflight:
The quick no-bullshit translation of this kind of crap is ALWAYS the same:
“Please spend more money on my kind of programs!”
I just sat in on a NASA talk about robotic exploration. Now, it’s true that
a robotic probe can do a great flyby of a moon. But when it comes to
actual planetary science, the quote went:
“A robotic probe can do in an afternoon what a human geologist
can do in 45 seconds.”
What really irritates me about the kind of evil we’re encountering
in the anti-space-exploration movement is its upending of basic
human values. Your tax dollars, my tax dollars are going to fund
both space exploration and space science. But space science
is fundamentally USELESS unless it serves some human goal.
In other words, if we’re not going to GO there, don’t waste my
money futzing around taking PICTURES of there, because,
“at the end of the day”, all you’re trying to do is kill human
spaceflight so you can keep taking money from me to pay
for your comfortable academic chair.
Get a life.
Mmm… sweet reasoning eases the pain.
What the hell? Visual Basic has gotten C++ style generics?
Will wonders never cease? What’s next, lambdas, continuations,
and currying? I’m almost scared to look. List comprehensions
I could handle, but if they go for APL-style array operations
I’m going to go have to have a little lie down for a while.
Now, this is somewhat sick … as soon as you
provide a nice feature for your users, like a
wiki, you run into asinine people who will
abuse it for their own purposes (follow the
This is why shopping centers have “no skateboarding”
signs and the BP on North Avenue closed off part
of its parking lot where the motorcycle clubs used
to pull in for their pit stops … not because any one
person doing it is bad, but when enough people
take advantage, things get screwed up.
At least this guy realized what he was doing was wrong:
Wiki Sandbox Morals
The Zealouts are coming!
Cool merging of the word zealot and lout!
I was working on an API and had trouble picking a name for
a particular operation (which we’ll call, say, “getCurrentText”
for sake of argument). TheFullyExplicitName was a little long
and unwieldy and I hve vry strng f3l’ns agst Un*x stle abbrs,
so I wanted to derive a simple text name that fits with the
rest of the API (read, readLine, isMoreNeeded).
So I ferret around on the web and find a few interesting
but no good resource for overall API names.
It seems to me there should be a standard lexicon of API
names. Just as there are standards for names in given languages
(e.g., getX/setX in Java, get/set properties in C#, -p predicates
in Lisp, isX for predicates in Java-like languages, etc.) there should
be standard names we can use for APIs with standard definitions
read/write or read/print
and so on. I guess there need to be two parts to this library:
the semantic list of terms that are common to many APIs, and
standard names that have maximum usage across the API’s
Anyway, just rambling.
Apparently it does.