The document discusses IronRuby, a dynamic language runtime (DLR) that allows interoperability with .NET through the use of the 'dynamic' keyword. It highlights the benefits and drawbacks of IronRuby, including lack of Visual Studio IDE integration and performance issues, while also pointing out future improvements. Additional resources and links for further information about IronRuby and the dynamic language are provided.

1. IronRuby and the Dynamic Language Runtime (DLR)Andre John Cruz19 December 2009

2. What’s IronRuby?

3. What’s a “Dynamic Language?”Expressive

4. Can change at runtime

5. FlexibleConcept of “Duck Typing”http://www.flickr.com/photos/guccibear2005/1387696735/

6. IronRuby Console and Ruby SyntaxFrom the command linedemo

7. The Dynamic Language Runtime (DLR)Rationale

8. Unified runtime

9. EmbeddableUsing IronRuby from C#CLR to DLR Interop using the “dynamic” keyword in .NET 4.0demo

10. Why?Why use a dynamic language?http://www.flickr.com/photos/petereed/496392956/

11. Scripting App SampleJimmy Schementi’sRubyConf 2009 Demodemo

12. DownsidesNo Visual Studio IDE IntegrationNo LINQ, .NET attribute supportLacking integration with .NET app frameworksPerformance hit

13. Future DirectionsVisual Studio IDE IntegrationLINQ, .NET attribute supportIntegration with .NET app frameworksPerformance improvements

14. Additional ResourcesOfficial Siteshttp://www.ironruby.nethttp://www.ironruby.infohttp://ironruby.codeplex.comhttp://www.ruby-lang.orgBlogshttp://blog.jimmy.schementi.comhttp://www.flanders.co.nzhttp://devpinoy.org/blogs/cruizer