10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Dionysios G. Synodinos on May 23, 2008
Ola Bini has been arguing that the world will not have a new big language again because developers will find value in choosing different languages depending on their problem domain. Similarly Martin Folwer has argued that programmers will choose a language for what it can do in the same way that they choose frameworks now. On the other hand Joe Winchester debates that you can only be master of one language.
Ola Bini, on one of his recent posts elaborates on the different strengths and weaknesses of the type systems of Haskell, Java and Ruby, which make these languages difficult if not impossible to compare:
So, we have three categories of languages here. The strongly statically checked ones, like Haskell. The weakly statically checked ones, like Java. And the dynamically checked ones, like Ruby. The way I look at these, they are good at very different things. They don't even compete in the same leagues. And comparing them is not really a valid point of reasoning.
Ola finds hope in polyglotism where:
A good programmer uses his common sense to provide the best value possible. That includes choosing the best language for the job. If Ruby allows you to provide functionality 5 times faster than the equivalent functionality with Java, you need to think about whether this is acceptable or not. On the one hand, Java has IDEs that make maintainability easier, but with the Ruby codebase you will end up maintaining a fifth of the size of the Java code base. Is that trade off acceptable? In some cases yes, in
Finally he advises to:
Be good polyglot programmers. The world will not have a new big language again, and you need to rewire your head to work in this environment.
Joe Winchester, describes a very different point of view, in the editorial of Java Developers Journal. He believes that:
It’s possible to be master of only one language- either that or Jack of all languages and master of none.
Joe recalls the attempts of the Smalltalk community to make Java run on their virtual machine (the Universal Virtual Machine - UVM) and why he feels it was a nightmare to code in such an environment.
Finally he proposes that:
… we should be fixing Java, not doing VM hacks and increasing complexity just to embrace other languages that didn’t even exist a few years ago.
If we don’t back Java as a language, rather than some kind of nebulus “Java technology” thing, we’re just dooming it to incognizance by diluting it with other languages and increasing the entropy required to build good software
On the other hand Martin Folwer, has also suggested that we may be entering such a period in which:
...will see multiple languages used in projects with people choosing a language for what it can do in the same way that people choose frameworks now.
and feels that a lot of things have changed since Smalltalk:
So are we returning to the language cacophony of the late 80's and early 90's? I think we will see multiple languages blathering away, but there will be an important difference. In the late 80's it was hard to get languages to inter-operate closely. These days there's a lot of attention to making environments that allow different language to co-exist closely. Scripting languages have traditionally had an intimate relationship with C. There's much effort to inter-operation on the JVM and CLR platforms. Too much has been invested in libraries for a language to ignore them.
There was actually an article on InfoQ last year that debated on if DSLs will bring the end of single language development.
What do you think? Will Polyglotism and DSLs become the dominant paradigm, leaving no room for a new “Next Big Language”?
Dionysios G. Synodinos is a Web Engineer and a freelance consultant, focusing on Web technologies
Getting Started with Stratos - an Open Source Cloud Platform
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Mobile and the New Two-Tiered Web Architecture
SOA All-In-One Guide: KPIs & Best Practices, ESB Report
18 agile and lean practices for effective software development governance
All the projects I did in the past years contained multiple languages: Java, SQL, Javascription, ActionScript, CSS, XSL... nobody complained about combaining all those languages: they are well suited for the domains they where created for. Adding more languages for specific domains (web developement, batch operations, high concurrency) is the logical next step.
Why does the link "Hacking 101 -The Top 10 Attacks in Web Applications" have a pdf icon next to it - it links to a presentation that requires realplayer?
So are we returning to the language cacophony of the late 80's and early 90's?
Yes. This is bound to happen anyway. I think it has more to do with two things:
It doesn't matter if you're in the Java camp, ex-Java camp, LAMP camp, or Microsoft camp. As far as languages go, there will be many. So you better get good at learning more than one.
Cheers,
Clinton
Because it would mean I, as a consultant, will be able to charge outlandish fees for fixing code in a project where the original authors have left the building, and new ones are hard to find. It will be like in the car mechanic business, where you can't just pick any car mechanic. You'll have to pick a car mechanic that knows your particular car. Good for the car mechanics, since they don't have to compete much, bad for the car owners.
/Mats
fixed :)
I take exception to a premise appearing in the title.
Java is not a big language. PL/1, C++, and C# 3.0 are big languages
Java is still a rather minimal language that any person worthy of the title of software engineer can readily master.
I do rather align with the notion of languages oriented to context situations. For instance, ActionScript3/MXML have just the right balance for the purpose of programming the web client tier. Java couple to BlazeDS and Spring Framework then gets reduced to a very straight forward matter of writing Spring POJO beans as services for the Flex clients.
Groovy and JRuby are getting to where performance is more reasonable. However, Java still offers static typing (as does ActionScript3). So if the SOA layer is going to be a large team affair, Java may remain the better choice, especially as OSGi bundles are used for deployment packaging.
For rules engines, Groovy and JRuby could be worthwhile - my bias is to Groovy as it is designed to be very close knit to Java.
I totally agree. C# and the only syntactically different VB.NET are huge languages and the tradition started from C# 1.0 and VB.NET 1.0 with that dreaded 'new' and 'new virtual' which makes inheritance and polymorphism daunting for the poor VB6 crowd who migh have been better off starting OOP with Java.
In C# 3.0 / VB 2008, there is LINQ. Java still looks tiny and lean even with 5.0 enhancements.
I think the author meant that Java is a big language in terms of its use and adoption, not its number of features. Just like before Java, C++ was the big language to know. He is suggesting that all programmers will have to know and use multiple languages in their projects and because of that, there will no longer be a single predominant language.
Big means big. It does mean using a single language to solve different problems instead of using different languages to solve different problems.
With LINQ, it looks like Microsoft's direction for C# and VB.NET
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
10 comments
Watch Thread Reply