Community
Ruby works on a much different development cycle, that relies on the code itself for documentation, and the blogosphere for consensus. This works well for rapidly developed low-risk projects, but is it right for the enterprise?
Philly Emerging Technologies Event: Call for Papers!
Often people take a look at JBI and expect to be developing new service engines and binding components, but more often than not an application developer won't need to code anything at all! (or at least thats the vision)
