The story of Ruby and Python in Silverlight

This is a really old thread from Michael on the IronPython Discussions
list, but while looking through old mail I found it and realized no one
ever directly replied to it. I read it over, and it made me realize
something; we rarely talk about “why” things happen at Microsoft on the
“outside” … we just throw code over the wall and expect you to
understand the “why” yourself. Granted, the IronPython/IronRuby team is
much better at including you, but you all are still in the dark about
why things are the way they are in Silverlight. Let me fix that …

This is my story of taking dynamic languages from Silverlight 1.1 Alpha
to Silverlight 2. Hopefully it clears up some confusion about why things
are the way they are, why they’re better off this way, and what we need
to do to make it even better.

Enjoy, and please let me know what you think of the current state of
Silverlight+Dynamic Languages in the comments.


This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs