.NET 和动态语言
当 Microsoft 开始发布 DLR 和相关语言时，您是否计划使用这些语言（例如 Iron Ruby 或 Iron Python）？
如果是这样，您这样做的动机是什么？
When Microsoft gets around to releasing the DLR and related languages are you planning on utilising those languages (such as Iron Ruby or Iron Python)?
If so, what are your motivations for doing so?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
是的，我当然打算找一些非必要的项目来熟悉 IronRuby。
我确信有一些真正的项目将受益于使用动态语言，但我不相信我可以正确判断，直到我用该语言编写了一些有意义的代码，所以我认为需要有意识地努力打破先有鸡还是先有蛋的情况。
我认为 IronRuby 将提供机会专注于该语言的新功能，而不会因新开发环境的差异而分心（我几乎是一个 C# 单一语言者）。
昨天我正在观看 IronRuby：正确的语言做正确的工作，这可能会影响我的回答 ;-）
Yes, I'm certainly planning to find some non-essential project to acquaint myself with IronRuby.
I'm sure there are real projects that will benefit form using a dynamic language but I don't believe I can properly judge that until I've written some meaningful code in the language, so I think it takes a conscious effort to break the chicken and egg situation.
I think IronRuby will provide the chance to concentrate on what's new in the language w/o being distracted by the difference of new development environment (I'm pretty much a C# monoglot).
I was waching IronRuby: The Right Language for the Right Job yesterday so that might be affecting my answer ;-)
是的，在某些情况下。
主要动机是重用已在 Ruby 和 Python 中实现的现有代码和库，以便更轻松地与用 C# 编写的其他代码进行交互。 对我来说，最重要的是跨语言集成的好处。
Yes in some cases.
Main motivation is to reuse existing code and libraries already implemented in Ruby and Python with easier interaction with other code written in C#. For me, its all about the cross-language integration benefits.
如果它们适合我正在从事的项目，我计划使用它们。 如果该项目同样可以轻松地用 C# 完成，我可能会坚持使用静态语言，因为
dynamic关键字将允许许多相同的功能。I plan on using them if they are right for the project I am working on. If the project is just as easily done in C#, I will probably stick to the static language, given that the
dynamickeyword is going to allow much of the same functionality.我不是 .NET 开发人员，但我会考虑以下条件来使用它：
I'm not a .NET developer, but I'd use it considering the following conditions:
大多数这些语言都可以在您的应用程序中托管，这就是有趣的地方。
如果您正在编写一个允许用户编写脚本以实现可扩展性的应用程序，那么您应该考虑使用它们。
Most of these languages can be hosted with in your application, and that's the interesting point.
If you are writing an application that allows your users to write scripts for extensibility, then you should consider using them.
我当然打算看看Cucumber。 同样，我认为如果我不至少看看 Rails 和 Django，那就太疏忽了。
I certainly intend to look at Cucumber. Equally I think it'd be negligent of me not to at least look at Rails and Django.
不。除了一些元编程（反射很糟糕）之外，动态语言与具有良好类型推断的静态类型语言相比并没有任何吸引力。
一方面，由于 IDE 性能不佳而造成的生产力损失是相当严重的。
No. Apart from some metaprogramming (Reflection sucks), dynamic languages don't really hold any appeal over statically typed languages with good type inference.
And the loss in productivity due to weak IDEs, for one, hurts quite a bit.