What advantages does using Oslo and M have and when would you use it?

Question

After attending a talk on Oslo/M I am struggling a bit to see the advantages of using it over existing methods and in what situation it would be useful.

I know its quite new and not all details have been released etc but can some one give me some advantages and when you might use it?

Thanks,

Alex

Answer 1

This questions seems to have the answer you're looking for:
What is model driven development good for?

Erik Wynne has a nice blog-post on this topic:
Oslo == 42

He also links to a post on MSDN, that contains some interesting thoughts:
Why do we need Oslo?

Answer 2

I haven't played with the Oslo alpha bits, but my understanding on a superficial level is:

• Trying to make it easier for developers to express and store their ideas in ways that make sense for the domain they are working in – i.e. domain modelling.

• Trying to make these stored ideas accessible during program execution.

So yet more of the trend towards declarative rather than procedural logic. That seems to be the way the development world is moving. I'm an old fogey, and far from convinced.

But we can't continue making software like an Egyptian pyramid, with millions of bricks piled on top of each other and no structural integrity, just brute force and thousands of slaves. So we need these new ideas.