I’m genuinely interested in .Net acquiring something like JetBrains MPS for creating textual DSL’s. I think Intentional Software’s platform sounds really cool (but it’s taken on a Duke Nukem Forever quality). However, I don’t get what Microsoft is up to with Oslo. This post from a member of the Oslo team who is responsible for explaining Oslo completely fails to explain Oslo: http://www.kraigbrockschmidt.com/luminarity/post/2009/09/08/What-Exactly-Does-One-Do-With-e2809cOsloe2809d.aspx#continue.
If someone else would like to interpret that post for me and explain it in the comments, I’m all ears (sincerely). Right now, I’m looking at Oslo and seeing nothing but a strange fixation on metadata and data modeling with little or no concern for the behavioral aspects of a system. I think the Oslo team is doing a very poor job explaining how that Oslo metadata can be used to drive behavior in an application and not taking enough into account how you’re going to connect Oslo metadata to the working code that actually makes it go. “All you need to do is parse the AST and…” is the equivalent of doing procedural programming against DataSet’s, but with a nastier API.
Why am I writing this? Because it would be really freaking cool if Oslo ended up being an awesome tool for me to efficiently build little textual DSL’s with a great tooling experience. That would rock. More data modeling tooling? Meh.