More than once, the last couple of weeks I repeatedly stumbled across situations in which I had to remember the infamous Law Of The Instrument in order to explain some peoples attitude towards technology and overall technological decisions. I am not sure if this “law” holds completely true all the time, but I am sure there are some valid points to it.
Looking back at yesterdays Dresden Eclipse Indigo demo camp, I ended up with a couple of thoughts in my mind, both related to the technologies demonstrated there, and related to how to make meaningful use of them in a real-world environment. Overally, this demo camp event mainly was dominated by topics related to modeling tools and concepts on top of Eclipse technology – hardly a surprise knowing that itemis, the company behind tools such as XText, also appeared as main sponsor and organizer of this evening. Consequently, XText also appeared on the agenda in its latest EMFText and how to easily build (or, better, “have around”) an Eclipse integrated debugger for EMFText based domain specific languages at no additional costs. Running a DSL interpreter and doing debugging just the way you’d do it in Java code surely is an interesting experience. Not even talking all too much about ProR integrated with XText for the purpose of capturing requirements in a somewhat formal way. In some situations, this is just what you want or need, and problems to eventually be solved by using these tools are obvious almost immediately…
For quite a while now we’ve been using Jython, a (re-)implementation of the Python programming language that runs on top of the Java VM and along the lines of JSR-223 (Scripting for the Java Platform), in our environment to deal with some use cases which addressed way easier using a scripting language than, in example, using Java code inside a webapp. However, so far our integration left a lot to be desired, so it was about time to get this things improved somehow.