This was old text from a previous draft of the article when we weren't sure what would be available on the MPS site. It was supposed to be removed, but slipped through the cracks. Our apologies.

There will be a prototype in the coming months, but it is not ready yet. We will correct the online version of the article as soon as possible.

Regards,

Rob Harwood

That is what we are actualy planning as the next step - we'll open the early access to MPS. We just need some time to clean it up. You can subscribe to RSS feed on this page to be notified about that.

- when looking at foreign MPS code, you have to understand the languages the other developer has designed. It will be important that languages are well designed, e.g. like usage of operator overloading etc.

It is the same as with class libraries - you need to learn it before using it. But in LOP the environment (editor) will help you to use new language - by providing languge-specific editor actions, autocompletion, refactorings, etc. And our experience shows that languages are much easier to learn then libraries, because they can be made much closer to the way people think about the problem domain.

- Will it be easy to migrate my code, when I want to switch towards a better DSL (if somebody wrote a better DSL for the same problem that I wrote one for)

The fact that programs in MPS are represented as trees and graphs means that you will not need to write parser for such transformation.

We also will provide special language that will allow to query/browse/change programs written in MPS, so yo can write these transformation scripts on a very high level, much easier then using existing approach, i.e. like source code API in IntelliJ IDEA.

So we'll make such kind transformation easier, at least it will become possible in MPS. Now for example it is almost impossible to transform UI code written in Java Swing to .Net's WinForms.

well, I really can't wait for the EAP !!

 

me too!