4 ms·
Here are some very interesting comments from the author: I guess with MS killing DLR and Iron languages, that puts more pressure on us, as I think this leaves
by euroclydon 16y ago
Here are some very interesting comments from the author:
I guess with MS killing DLR and Iron languages, that puts more pressure on us, as I think this leaves Irony as the only ongoing technology for parser/interpreter construction in .NET. DLR, in my humble opinion, had never had a slight chance to become mainstream - it's just too complex, and benefits (like performance) are non-existent.
there are other gaping holes in .NET technology, which are screaming "fix me!", and which are more relevant to biz app programmer like myself. Entity framework and LightSwitch are jokes and don't even deserve any serious discussion. That's what I'm trying to do now - fill the void, and sorry to those who work in areas where parsers are more important than anything else.
- profquail 16y agoI don't know why the author thinks that there aren't any other parser/interpreters for .NET; I'll grant that there aren't many, but ANTLR still supports C#, and I've been using fslex/fsyacc recently (found in the F# PowerPack). There's also FParsec if you prefer a parser-combinator approach.
- thibaut_barrere 16y agoWhat makes him tell that MS is killing the DLR and Iron languages ? From my understanding both got funded by MS then passed on the community (the IronRuby mailing list is pretty active these days), but I wouldn't say MS killed these projects.
- bradhe 16y agoNot at all. IronPython is alive and well and (as I understand it) MS' bet for embedded scripting (at least, that's what they're recommending).