Half a Year in Review – The Top Ten Ruby and Rails Happenings in ‘08

by Robert Dempsey on July 3, 2008

The first half of 2008 has seen a great number of happenings in the Ruby and Rails worlds. Here are the top ten for the first half of 2008.

  • June 23, 2008 – Rails scales – LinkedIn serves 1 billion pages using Rails
  • June 1, 2008 – Rails 2.1 is released
  • May 31, 2008 – Ruby 1.8.7 is released
  • May 30, 2008 – Joel Spolsky keynotes RailsConf 2008
  • May 30, 2008 – FiveRuns released TuneUp to help with Rails performance optimization
  • May 27, 2008 – JRuby 1.1.2 is released, and runs Rails 2.1 like a champ
  • April 13, 2008 – Phusion Passenger (mod_rails) is released
  • April 11, 2008 – Rails core moves to Github, prompting many to move with them
  • April 2, 2008 – Morph Labs makes Rails deployments to EC2 a cinch
  • January 1, 2008 – Thin comes on the scene as an alternative to Mongrel

See something I missed? Drop us a comment below.

Bookmark and Share

Other Posts That Might Interest You

  1. FlexibleRails – Integrating Flex and Rails – Review coming soon
  2. Ruby on Rails 2.1 Released
  3. Thin – a new web server for Ruby
  • Joel Spolsky talking at RailsConf is a significant event? Really? :)

    If I had to add anything, it'd probably be the significant of Euruko 2008. It holds a distinction as the first, heavily attended (as in, over 200 people) European Ruby conference (something that was a long time coming).

    Alternatively, Rubinius running Rails, the launch of Dave Thomas' screencast series, the initial release of MacRuby, the launch of RubyFlow, Ruby getting its own Reddit, Microsoft's attempts to get Ruby into Silverlight, etc.
  • The LinkedIn reference is a little misleading. As Steven surmised, LinkedIn is 99% Java. However, they have deployed a RoR Facebook application that is serving 1 billion page views per month as discussed here:
    http://blogs.zdnet.com/enterprisealley/?p=188
  • Steven
    Any links for each event? I thouht LinkedIn is Java-based...
blog comments powered by Disqus

Previous post:

Next post: