Tracking change and innovation in the enterprise software development community
Free Book Offer
SOA Demystified
$40 Value
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Abel Avram on Aug 24, 2008
In this interview made by Sadek Drobi during QCon San Francisco 2007, Neal Ford talks about the tendency of having multiple languages running on one of the two major platforms existing today: Java and .NET. He also presents the advantages offered by Ruby compared to static languages like Java or C#.
Watch: Neal Ford On Programming Languages and Platforms (32 min)
Neal talks about the need of developing languages, like Ruby and Groovy, to run on top of the JVM due to limitations of the Java language. Ruby, he says, is a powerful dynamic language offering the programmer the ability to write cool stuff in simple ways, giving him more flexibility and increasing his productivity.
Neal also talks a lot about meta-programming. He notices the limited meta-programming features existing in Java, and makes a case for the meta-programming support existing in Ruby.
Neal thinks that in the next decade, we will see several, some of them specialized, languages running on the most prominent platforms existing today, Java and .NET. This combination of languages-platforms allow the developers to choose the most efficient language for a specific task while not having to worry about deploying the resulting code since it runs on well tested and proven platforms.
Innovation in Your Data Centre
The 5 Mandates of Software Development Teams - Presto Manifesto
Understand and Align BPM, SOA, and Lean Six Sigma: 43 page IBM Redguide
I have heard Neal Ford use the term "priesthood" in one or two of his talks. I'm sure he meant that instead of "pre-stood" as transcribed above.
"it was trying to be backwards compatible with C and C++ to attract members that pre-stood." should be "it was trying to be backwards compatible with C and C++ to attract members *of* that *priesthood*."
Should be called, Why you should switch to Ruby from Java!
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
2 comments
Watch Thread Reply