Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Niclas Nilsson on Jan 03, 2008 07:42 PM
The trend seems to be clear; in the next few years there will an increase in adoption of new programming languages. Not primarily to replace the ones we currently use, but to mix languages and use the right language for the problem.
But what is the right language for a particular problem? In a recent blog post, JRuby developer Ola Bini dives into the topic from a new angle. Multi-lingual programming, also known as polyglot programming, has been covered earlier by InfoQ, but Bini describes the phenomenon in the context of how we may build future systems; which types of languages we may use - and for what.
Bini describes three different layers and the languages, or rather language types, that fits into these layers. No, not the classical presentation, business, and data layers; Bini slices the world differently:
Bini describes the stable layer:
The first layer is what I called the stable layer. It’s not a very large part of the application in terms of functionality. But it’s the part that everything else builds on top off, and is as such a very important part of it. This layer is the layer where static type safety will really help.
The dynamic layer is where most of the application functionality exists:
The second layer is the dynamic layer. This is where maybe half the application code resides. The language types here are predominantly dynamic, strongly typed languages […]
Also considering the dynamic layer, he adds:
It’s a nice and productive place to be, and obviously, with my fascination for JVM languages, I believe that it’s the interplay between this layer and the stable layer that is really powerful.
In the domain layer, Bini bets on the emergent DSL movement.
The third layer is the domain layer. It should be implemented in DSL’s, one or many depending on the needs of the system. In most cases it’s probably enough to implement it as an internal DSL within the dynamic layer, and in those cases the second and third layer are not as easily distinguishable. But in some cases it’s warranted to have an external DSL that can be interacted with. A typical example might be something like a rules engine (like Drools).
David N. Welton wrote a response to Bini’s post, where he describes his doubts about this evolution:
I’m dubious, and wonder what he would consider to be the underlying sociological and economic factors driving this change. Programming languages are, in the end, about people in all their weirdness, so to understand where languages are going to go, you have to consider those human factors […]
Welton refers to an article he wrote a couple of years ago that analyzes the economics of programming languages. In the article, Welton finds that since most language implementations are free today, the only way to get better economics using a new language is if it makes the code:
Ola Bini wraps up by explaining that he does not believe in the next big language, even within one layer:
But I need to make one thing clear - I don’t believe there will be a winner at any of these layers. In fact, I think it would be a clearly bad thing if any one language won at any layer. That means, I’m seeing a future where we have Jython and JRuby and Rhino and several other languages coexisting at the same layer. There doesn’t need to be any rivalry or language wars.
Bini has done big contributions to make mixing languages on virtual machine level possible by his work on JRuby, and many other have done the same for other languages. On the other big virtual machine platform, Microsoft prepared for multiple languages from the start by providing VB.NET, C# and C++ implementations for the Common Language Runtime. Recently, they also released the Dynamic Language Runtime, on top of which IronPython and IronRuby is built, which emphasizes that .NET is a multi-language platform.
But the article still leaves interesting questions:
In short, how will future systems utilize programming languages?
The Role of Open Source in Data Integration
Intel® SOA Expressway Performance Comparison to IBM® DataPower XI50
Download the Free Adobe® Flex® Builder 3 Trial
SOAsocial.com - See what the SOA community is Talking About
Comprehensive Threat Protection for REST, SOA, and Web 2.0 Applications
This is a great coverage of the topic by Niclas Nilsson. I expect a lot of discussion with all the intelligent, visionary, and experienced programmers to gather here and comment. It looks like my comments are the first ones on this thread. But, I encourage a lot of feedback coming from many industry leaders. Wake up, guys!! My experience has been limited to one language Java, and C++ from way past. I've been also using Java-based frameworks a whole lot. But, regarding topics such as CLR, JVM, DSL, I expect multiple comments pouring in at this thread from multiple leaders in the industry. Best regards, Abhay
A lot of interest in this thread is seen at: http://www.dzone.com/links/programming_languages_in_future_systems.html
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
2 comments
Watch Thread Reply