PERL,INGRES,PROGRAMMING

Why were the DLR based languages such as IronPython and IronRuby gone defunct? Were they victims of their success in that they were competent competitors to the .NET languages like C#? Scott Hunter's response: There were points in time where with .NET we just tried to do too many things at the same time. The DLR languages were more victims of us just trying to focus the basics of .NET again. During that time frame we were building new web frameworks based on competition and starting our open source journey. Back then we gave customers so many options that it made the platform appear more complicated. on medium

InfoQ expands on the IronJS i-programmer interview

We set out to investigate what it takes to implement a dynamic language for the .NET platform and the DLR, and what better way than to ask someone that has already done it. So we interviewed Fredrik Holmström who has successfully ported Javascript under the name of IronJS, consistent with the naming pattern of the .NET dynamic languages like IronRuby or IronPython. We discovered what possibilities a dynamic language adds on top of the static CLR languages, what the porting process is, as well as a deep look into the IronJS internals. Full article on i-programmer

Just finished reviewing Pro DLR in .NET 4.0. Book review at i-programmer