# Insight on the future of IronRuby?

**URL:** <https://www.ruby-forum.com/t/insight-on-the-future-of-ironruby/195827>\
**Category:** IronRuby\
**Created:** [September 30, 2010, 9:44pm UTC](https://www.ruby-forum.com/t/insight-on-the-future-of-ironruby/195827 "2010-09-30T21:44:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thbar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@thbar](https://www.ruby-forum.com/u/thbar)\
**Post date:** [September 30, 2010, 9:44pm UTC](https://www.ruby-forum.com/t/insight-on-the-future-of-ironruby/195827/1 "2010-09-30T21:44:01Z")

</div>

Hi guys (and girls, if any),

I’d really, really like to have any hint of where IronRuby and the DLR  
are  
going, roughly.

We’re considering using IR as a scripting engine for a fairly important  
desktop app, so I thought I would ask, now that the dust has settled.

Any idea ?

thanks!

– Thibaut

---

<div class="post-metadata">

**Author:** ![thbar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@thbar](https://www.ruby-forum.com/u/thbar)\
**Post date:** [October 1, 2010, 11:31pm UTC](https://www.ruby-forum.com/t/insight-on-the-future-of-ironruby/195827/2 "2010-10-01T23:31:29Z")

</div>

Is there any “official” work from Microsoft about these issues?

Thibaut Barrère wrote:

> Hi guys (and girls, if any),
> 
> I’d really, really like to have any hint of where IronRuby and the DLR  
> are  
> going, roughly.
> 
> We’re considering using IR as a scripting engine for a fairly important  
> desktop app, so I thought I would ask, now that the dust has settled.
> 
> Any idea ?
> 
> thanks!
> 
> – Thibaut

---

<div class="post-metadata">

**Author:** ![thbar](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/t/eb8c5e/32.png) [@thbar](https://www.ruby-forum.com/u/thbar)\
**Post date:** [October 2, 2010, 12:34am UTC](https://www.ruby-forum.com/t/insight-on-the-future-of-ironruby/195827/3 "2010-10-02T00:34:07Z")

</div>

The official Microsoft position remains the same:

“At this time, we have no announcements to make beyond what we announced  
in July 2010 — that we were putting these [IronRuby and IronPython]  
under the Apache License v2.0. Clearly, there is customer and community  
interest in these languages. With many organizations running mixed IT  
environments, we continue to value community feedback on how we can  
support their interoperability needs, and we remain committed to  
supporting multiple tools and languages that provide developers with the  
most choice and flexibility.”

Tomas