Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Mirko Stocker on Oct 08, 2008
On Friday the 3rd, Ruby 1.9.0-5 was released by Yuki Sonoda, after the last delays, related to miniunit, were fixed by Ryan Davis. This release also marks the feature freeze for the upcoming version 1.9.1. (see the changelog for detailed information).
Marcin Mielżyński, one of the JRuby committers, proposed to drop support for Ruby 1.8.7 in JRuby:
Most 1.8.7 features that came from 1.9.1 are to make transition from 1.8 to 1.9 series easier. Majority of them is just a copy (with minor changes to match 1.8.x api), but there is a lot of tricky examples that behave differently under 1.9.x, 1.8.6 and 1.8.7 [...] it doesn't make sense to port all the behavior from 1.9.x to 1.8.7 since it would end up 1.9.x just without yarv and all the fancy syntax features (well, and encoding support of course).
Thomas Enebo and Charles Nutter agreed and added, that users should switch directly to 1.9 rather then writing code that only works in 1.8.7 (support for Ruby 1.9 in JRuby can be enabled with --1.9). Charles also posted their decision to the Ruby-core mailinglist., but no discussion has started yet.
Ruby uses the ===-operator to compare the different cases in a case-statement. Ruby 1.9's Proc class just recently got a ===-method, basically just an alias for the call-method used to invoke the Proc. Now, this means that one can use a Proc object in a case-statement; it will get the case-argument as parameter. This trick was discovered by Aimred, who added the method themselves, before Matz integrated it into Ruby 1.9.
Dave Thomas shows an even more sophisticated application, using currying to create several Procs to check for the day of the week.
Architectures Behind Facebook, Skype, Sky.com, Bwin, League of Legends @ QConLondon
Agile Development: A Manager's Roadmap for Success
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
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.
1 comment
Watch Thread Reply