Tracking change and innovation in the enterprise software development community
Testing Tools to
Support Agile
Software Delivery
Whitepaper
In this presentation from the JVM Languages Summit 2008, Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library method access, method call semantics, scopes, open classes, heap-based frames, library challenges, strings, regexps, I/O, green threads, POSIX features, C lib support and future plans.
A few patches by Brent Roman promise to fix a long standing issue of memory leaks, particularly for continuations, for Ruby 1.8.x. They also happen to improve performance.
Looking back at the year that is coming to its conclusion, we wanted to have a retrospective and find out which were the most read news and exclusive content items during 2008. We compiled a list containing top 5 news for each community and top 3 exclusive content items for each type: articles, interviews and presentations. This list considers the number of unique readers for each news.
This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Keynotes, Interviews, RESTFul Web Integration in Practice, Solutions Track, Performance and Scalability, Being Agile, Ruby in the Enterprise, Cloud Computing, Functional/Concurrent Programming Applied, Effective design and Clean code, and many more!
Aptana RadRails: An IDE for Rails Development by Javier Ramírez discusses the latest Aptana RadRails IDE, a development environment for creating Ruby on Rails applications. The book's publisher, Packt Publishing, also provided InfoQ with an excerpt from Chapter 7 of the book, entitled RadRails Views.
In this interview from RubyFringe, Yehuda Katz talks about Merb, its design principles, and how it differs from Rails. Yehuda also mentions Yard, an RDoc replacement.
In this interview from RubyFringe, John Lam talks about his work on IronRuby and how Microsoft is approaching Open Source software development.
Developer-driven testing is probably the most influential software development technique of the last 10-15 years. There's no question that it has improved the practice of building software. And in a dynamic language like Ruby, it's hard to get by without it. But is it really the best way to find defects? Or is the emphasis on testing and test coverage barking up the wrong tree?
In this RubyFringe talk, Reginald Braithwaite shows how to write Ruby that reads, writes, and rewrites Ruby. The demos include extending the Ruby language with conditional expressions, new forms of evaluation such as call-by-name and call-by-need, and more.
The Humble Little Ruby Book covers the base syntax of the language, including working with values, flow control, and object oriented programming, into some of the library functionality of Ruby, such as databases, web services, and string manipulation.
