Subscribe via RSS

Season 2 Episode 2: IronRuby at FOSDEM – Ivan Porto Carrero Interview

By codemongrel

As volcanos rage in Europe, Open Source rumbles in Ireland, as we seem to be smack bang in the middle of conference season! Somewhere between OSSBarcamp just gone and the Open Spaces Coding Day coming up we’ve managed to get a chance to mixdown a very interesting interview from FOSDEM with IronRuby contributor Ivan Porto Carrero.

 

Ivan is the author of IronRuby in Action, published by Manning, a comprehensive and hands on introduction to IronRuby – an implementation of Ruby which runs on top of .NET (including Mono). This allows you, for example, to easily develop Ruby plugins for Mono apps such as Banshee on Ubuntu, as well bringing the power of Ruby to a wide range of developers working with .NET on Windows. The timing of this podcast couldn’t be better as the official IronRuby 1.0 release is just out!

 

If this kind of thing tickles your fancy then you’re well encouraged to come along to the Irish Open Spaces Coding Day taking place at UCD Open Source Labs on April 24th!

 

 

As with last year, if you’ve any feedback please send it on via our twitter account (codemongrel) or post a comment below! We’d love to hear your opinion.

 

Season 2 Episode 2 is available at the following links (high quality formats recommended)

Running time 13:38.

 

You can subscribe to the Code Mongrel podcast using this RSS link or iTunes.

 

Music by Josh Woodward (Sticky Bee), see joshwoodward.com

 

Show Notes

 

Creative Commons License

 

Code Mongrel Podcast by Code Mongrel is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.

1 Response to Season 2 Episode 2: IronRuby at FOSDEM – Ivan Porto Carrero Interview

  1. Billy Stack

    Excellent podcast. Very excited about this whole IronRuby thing. Especially interested in the way Ivan explains that “mocking” is much easier than e.g. Rhino Mocks. Currently in the .NET space, introducing any mocking code into a test substantially clutters the readibility. Ruby/IronRuby based tests will hopefully solve this.

Post a Comment