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.
How would you like to view the presentation?
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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
18 agile and lean practices for effective software development governance
In the description, of IronRuby there is a rather dismissive reference to being able to mix your IronRuby with your IronPython and your C#, followed by "Why would you want to do that, except to torture your developers". This is then almost immediately followed with the glowing review of JRuby which is fantastic "because you can use all your Java code". Hmmm...
IronRuby and JRuby are in concept identical, i.e. both are implementations on top of VMs that can run other languages, which may or may not be languages that you have legacy code in. So how is this something puzzling on .NET and at the same time the thing that makes JRuby great?
3 answers:
- Java language is more involve in lots of cross platform open source project
- Apparently performance of jruby seems better than ironruby
blog.prokrams.com/2008/08/27/ironruby-vs-jruby-...
antoniocangiano.com/2008/12/09/the-great-ruby-s...
- I think that Ruby to run .net programs is cool, but Ruby to run ironPython doesn't seem cool.
Jojo
I'm sorry, but none of answers addresses why language interop in the jvm is great, but in the clr it's something you'd to do torture developers. At that point it's just a value judgment of "i like java, but i don't like .net", which may be a valid opinion, but sort of irrelevant in a Ruby VM comparison.
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.
3 comments
Watch Thread Reply