Tim Bray moves to Sun

Tim Bray, one of the authors of the XML spec, has moved to Sun:
http://www.tbray.org/ongoing/When/200x/2004/03/15/SunnyBoy

He's not a Python user -- most of the XML-mangling scripts he's posted are
in Perl -- but the above post contains the following:

    In fact I personally believe that Java's share of enterprise software
    will decline, but not in favor of anything from Redmond. I think that
    dynamic languages (Python and friends), particularly in conjunction with
    Test-Driven Development, are looking more like winners all the time.
    They generally are cheaper to program in, run just as fast, and have
    fewer bugs; what's not to like? There is one huge niche that the
    strongly-typed statically-compiled languages are never going to be
    driven out of, but I'll save writing about that for later because I've
    got a major skunkworks in mind.
    
His position is described as "next gen tech and standards development at the
intersection of RSS, XML and advanced search technologies".  At the end of
the post, he says:

   If you know me and you need to get a message into Sun, and you can
   convince me that Sun needs to hear it, I might be able to help. Probably
   not much off the top, I'm still learning where the toilets are. But
   eventually.
   
What's the Python relevance of all this?
   
I think we need to tell Sun that they should adopt Python as a standard
scripting language for Java.
   
The pros for the Python community are obvious, I trust.  Advantages for
Sun:

* Fills a gap in the Java API, making it easier to write tests/script
  applications/etc.
  
* Jython is one of the most widely used Java scripting languages (impossible
  to say if it's the most widely used one)
* Shows that the JVM can be multilanguage and provides a response to
  .NET's support of C# and Visual Basic.
* Python is not new, not a flash-in-the-pan; there's an existing user
  community, libraries, books, etc.
	
Cons for Sun:
* They may not want to choose a horse in the scripting language field.
* They might prefer to invent their own (with more Java-like syntax?
  that they can control?).
	  
What should be done about this?  I could just drop Bray a note, of course.
But should this be done more formally?  Should we or the PSF assemble a
white paper or presentation that can be given to whatever executive is
responsible? (If Guido ever runs into James Gosling at a conference, he
could talk to him, of course, but I don't think Gosling is Java BDFL in the
strategic sense.)

--amk