[ruby-talk:02332] Ruby-Python fusion?

Usually I give some time for news to settle before I pass the word, but
this case has emergency priority. At least for me.

Have you read from comp.lang.misc (crossposted to c.l.python) 
Yukihiro Matsumoto's detailed proposition how Ruby development should be
merged to the development of forecoming Python versions.

I quote few pieces, in case you don't have news access (this will be at
deja.com within hours, at least in days):

"I've been watching Python development for seven years and I'm therefore 
able to announce it's crisis. Python has been progressing nicely
during that time, but it's core features are way too simplified to answer
modern demands. As an answer to newer requirements many parties have took
action on their own hands and are developing next-generation Python. Some
of these advancements might go through Guido and even appear in Python
2.0, but it's too late then. 'Better' versions continue to flourish and
split Python community. In no time there will not be just one community."

...

"Only way I can see Python might survive is to focus development into one
common goal: newer, better, a little bit more complex Python. In fact much
of this work is already done. You can explore some ideas what to expect in
'Python 4000' by visiting www.ruby-lang.org and testing it's stable code
base. Let's unite as communities and combine Ruby's  power into
Python!"

...

"Now, if somebody wonders why I'm willing to loose my grip on Ruby for
'better world(tm)' that's based purely on the fact my fusion engine
doesn't have any fuel left. This one-man-expedition has conquered the
worlds that it had power to explore. I'm quite tired to apply any single
patch more while it's quite easy nowadays because there isn't any big
leakages left. Ruby has matured and I'm feeling myself a proud and very
old father. It wasn't easy language to get over puberty, but it managed
and so did I! :-)"