BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Dynamic Languages Content on InfoQ

  • InfoQ Changelog

    InfoQ maintains a version number tied to new features developed for the site as a means to communicate progress to its audience. v1.1.5 is the latest version. InfoQ initially launced at 0.6 last year.

  • Coming From Ruby

    Do you "come from" a particular programming language? If so, that's great — but don't forget to take each language on its own terms. David A. Black shares some thoughts about "coming from" a language, and the etiquette of language travel, in the context of the recent history of Ruby.

  • The MOle Plugin

    The MOle, so named because it acts as the investigators agent, is a plugin that provides insight into the inner workings of Ruby on Rails in realtime, as requests come in and get processed. The author describes how the plugin came about and gives InfoQ readers a detailed introduction to his innovative plugin.

  • Adding Properties to Ruby Metaprogramatically

    Werner Schuster walks us through a simple example of adding Java-style properties support (declarative getters, setters and change listeners) to Ruby classes via a Mixin by using elements of meta-programming. Introduces ideas for enhancement using principles of design-by-contract and pluggable type systems.

  • Interview: Jérome Louvel about Restlet

    In this exclusive InfoQ interview, Jérome Louvel talks about Restlet, a Java framework for building Web applications following the REST architectural style. Topics covered include the reason for Restlet's existence, REST support in Web services frameworks and in Ruby on Rails, expectations for JSR 311 and Restlet's roadmap.

  • Ruby on Rails case study: ChangingThePresent.org

    Bruce Tate, author and CTO of ChangingThePresent.org gives a glimpse inside the day to day operations of ChangeThePresent.org with a broad overview of how his team works, the technology trusted for production environments, tools, and most important Rails frameworks.

  • Key Takeaway Points and Lessons Learned from QCon London 2007

    This article presents the main takeway points and further reading as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Case studies (amazon, eBay, Yahoo!) Java, Agile, the Agile Open Space, Qualities in Architecture, Ajax and Browser Apps, .NET, Ruby, SOA, Usability, Banking Architectures followed by a summary of peoples over all opinions of QCon.

  • Versatile RESTful APIs Beyond XML

    The world of RESTful resources that Rails firmly entered with version 1.2 naturally uses XML as its lingua franca. But there's no reason that it can't be multi-lingual, and thanks to the versatility of rails it's easy to support other standards alongside XML in our RESTful applications, potentially opening them up to a wider audience and/or reducing their bandwidth requirements.

  • Introduction to ActiveMessaging for Rails

    The maintainer of ActiveMessaging for Ruby on Rails gives a comprehensive and informative introduction to his open-source framework, which enables enterprise messaging technologies to be easily integrated with Ruby on Rails applications, and is getting support from noted industry leaders such as James Strachan and Jon Tirsen.

  • Evaluation Options in Ruby

    Jay Fields, known for his cutting edge work defining BNLs (Business Natural Languages) delivers a code-rich explanation of eval, class_eval, and instance_eval, in the context of implementing domain-specific languages in Ruby.

  • InfoQ Book Excerpt: Rails for Java Developers

    Rails for Java Programmers, by Stuart Halloway and Justin Gehtland, teaches the Rails framework to Java developers. It provides an overview of Ruby, comparing and contrasting with Java and then gives a detailed look at the Ruby on Rails framework and compares each piece against the best known Java equivalent. This InfoQ excerpt includes sections on controllers, core classes, and unit testing.

  • ORM with DrySQL and ActiveRecord

    ActiveRecord fails the DRY principle, especially if your database doesn't follow Rails naming conventions. As well, ActiveRecord associations and validations are redundant specifications of database constraints. Bryan wants to avoid (as much as possible) the situation where he's averse to making changes to his database schema, because of the resulting effort to change his app code.

BT