This is just another one of those boring weekends where I felt the need to hack on something. If you follow Google Chrome's blog you're probably aware of this little nifty feature they started to implement in their latest builds: HTML5 voice recognition. And that's when it struck me: "Hey, what if I use that and tweet with my voice instead of typing?" The result of this hacking session is LoudParrot, a sample Rails app that shows how to do just that.

Since I started working with Ruby about 4 years ago, I've used quite a few text editors and ide's: RadRails, gedit + plugins, TextMate and Vim. TextMate is the one I've used the most and it's been ok for a long time. Until you realize you need half a dozen bundles to make it really useful for ruby development. Obviously the same goes for Vim and gedit. Oh, and forget about refactoring.

Last Tuesday I gave a short presentation on the whole Clouds Against the Floods thing at the Ruby on Rails Oceania User Group here in Sydney. Those guys are awesome and they recorded the talk - thanks guys! If you'd like to download the slides, they're available on Slideshare. Enjoy! ;)

This is just a quick post to let you know that AppConstants can now be used as gem! Just add it to your Gemfile and 'bundle install' it: #in your Gemfile gem "app_constants" #in the console $ bundle install $ rails generate app_constants #then follow the instructions on-screen instructions It can also be used without Rails. Check out full instructions on the GitHub repository. Feedback welcome :)

I think by now everyone's heard of the hard time the guys up in Queensland, Australia are having because of the recent floods. People have lost their lives and many others have lost their homes and businesses, product of years of hard work. As a result of this massive disaster the Queensland Government decided to run a telethon to encourage donations to help the flood victims. The Telethon aired last Sunday, 09/01/11, on Channel 9 and lasted for 2 hours.

It's been now over a week since we moved to Sydney and everything is just great. We're still house hunting but I got a feeling we'll have a home soon. :) In the meantime, this morning I got a feature request on github to allow AppConstants to interpret YAML files with embedded code like this: I haven't needed it myself but thought it would be a nice addition so my latest commit does exactly that.

Back in January I announced a small but useful plugin called AppConstants, that basically provides a central place where you can store environment specific constants. And since I started using Rails 3 in the past week, I thought I'd make it Rails 3 compatible. The code is really simple and - as I expected - the upgrade process was quite straight forward. I'm not gonna write a guide here on how to upgrade your plugins to Rails 3 - there is plenty about that around the web - but instead, just show the steps I went through to upgrade mine.

Learning new programming languages is fun. And if it's your 2nd, 3rd...Nth programming language you will eventually look for features you already know and love. Coming from Ruby - but after having done my fair amount of Java for many years, among other things - I end up looking for features like blocks, open classes and syntax sugar like automatic generation of attribute accessors. These are hard to let go of.

What? In Ruby you have basically two ways of defining private methods: I see a small problem with both approaches. In the first one, and the most obvious, is that you need to duplicate the method name as well as add an extra method call - private - just to change its visibility. The second approach avoids this but adds the risk of accidentally putting a method that is intended to be public under the private section of the source file, which can render an annoying debugging session.

Today I read a nice post - in Portuguese - by Fábio Akita on how to manage multiple ruby versions on your machine. I've tried it once with some tool I can't even remember the name but failed miserably. But this time things look very different. The tool here is the rvm - short for Ruby Version manager - and it works just great. Let's cut to the chase and imagine that you, like me, want to run/develop/test your code on both ruby 1.

Yesterday I've done something I should do more often: Revisit some code written a while ago for our current project and make it better. Let's face it. We all write crappy code the 1st time. The difference is in what we do about it afterwards. We might decide it's good enough and keep moving, or we could (and should!) stop and refactor it! The code I revisited worked as a refactoring exercise and it's initial version is shown below: class Jphoto .

I'll be speaking at this year's Rails Summit Latin America in Sao Paulo, Brazil. It will be a good opportunity to meet some amazing people and visit friends back home! :) Overall I'll be spending 12 days in Brazil, with 2 of them dedicated to the conference. The other 10 I'll be in Rio de Janeiro visiting my family and friends. I strongly advise you to spend some time in Rio too, if at all possible.

Update: The service is now down while we move it from the VPS provided by Rails Rumble to our own. I'll let you know once it's up. Last weekend Philip, Pedro and myself got together for this year's Rails Rumble. We haven't had really decided what to do until a few days before the competition, but I had this really simple idea and decided to go with it. Seems people liked it, given a few positive comments we received.

- Overall results First off, I'd like to thank everyone who voted on this poll. With a total of 236 votes, here is the summary of the first two questions: - Are you currently working with or researching about language alternatives for the JVM? - e.g. JRuby, Scala, Groovy {% img /assets/images/scala_improvements.png %} Tooling. The majority of comment urge for better tooling and IDE support. That simple. - Others

Do you know? I didn't. And started to get annoyed by using these terms interchangeably and not really knowing the difference. There are a few. And they are subtle. I don't think most of us would ever have problems with it but it's the kind of information you'll be glad to know when having those weird behaviors in your code on a Friday at 6:01 pm, just before pushing to production.

Wanna help improve JRuby? Make sure you read this post by Charles Nutter first. There he explains how to run Ruby specs with JRuby. Start with fixing Ruby specs is a great way to get acquainted with the code. And it’s also a important task in order to make sure JRuby is the most complete and compatible ruby implementation out there. But before you get your hands dirty, it will be a lot easier if you can actually debug JRuby’s source while fixing any specs - or bugs/features for that matter.

As always I expected a good talk from Ola and once more he delivered it. But this one was different. It might have been even boring to some ruby developers since we saw a fair amount of java code in this presentation. Ola gave us a tour through the main classes that make JRuby possible with a single purpose: so we can check out the code and hack ourselves. You can download his slides here.

As you probably know, since rails 2.1 you can write test methods in the following format: test "hotel should return its permalink" do #your test code here end Which is great, as the test name becomes much more clear. But you can't simply run this test easily from the command line. You'd have to run something like: $ ruby your_test_file.rb -n test_hotel_should_return_its_permalink It annoys me. And it's not practical either to make the test fail just so you can get the test's real name.

There are several ways you can measure your rails application's performance. The techniques range from filling your code with "puts" statements - :p - to fancy ones like NewRelic - which is quite nice, I must say. But what many people don't know is that rails ships with a handful of scripts to help you out. One of which is called profiler, located under your application's scripts/performance directory. By default it uses the standard ruby profiler but if you want more speed - and additional reporting options - , consider installing the ruby-prof gem.

As you may already know, Merb turned 1.0 a while ago and I decided to resume my studies to learn the framework. So I just built a new app with a few resources and fired the migration scripts: $ rake db:automigrate And this is what I got: Loading init file from /Users/leo/projects/merb/my-first-app/config/init.rb Loading /Users/leo/projects/merb/my-first-app/config/environments/development.rb ~ Connecting to database... /opt/local/lib/ruby/gems/1.8/gems/dm-core-0.9.6/lib/dm-core/adapters/data_objects_adapter.rb:137:in `initialize': wrong number of arguments (8 for 1) (ArgumentError)

This post is just to clarify some confusion I've noticed reading some posts around the web. There is some misunderstanding of the differences between Ruby 1.8 and Ruby 1.9 regarding threads. And the difference between them and JRuby. So I decided to write this small summary: Ruby 1.8 - Supports only Green Threads This means that the ruby interpreter has its own scheduler. No matter how many threads you create in your ruby program, there will be only one native thread on your OS.

REXML is the standard XML processing library for Ruby. It's on Ruby's core and is terribly slow. Yeah, I know it's pretty simple to use, got a nice interface and, again, it's just there. And it is a good library, for most things. But if you, as me, came to a point that processing XML is taking 50% of the time to render a rails action, it's time to change.

I'm back in Madrid again after the RailsConf and I think it's time to say something about it. :) First off, the infrastructure provided by the conference was really great. The rooms, WiFi connection, food... Really well organized. Now to the sessions, highlights: Tutorials (Tuesday) - Meta-programming Ruby for fun and profit (Neal Ford, Patrick Farley) The old and good techniques that made Ruby so powerful. Here Neal and Patrick walked us through the main tricks to meta programming like open classes - and conditionally open them - , dynamically define methods, sending messages to objects and how Ruby can help test your Java code in a much easier way.

The title says it already. On monday I'll be going to Berlin to attend this year´s RailsConf. This will be my first one and of course my expectations are pretty high! As usual, after the conference I'll try and give a summary of what happened there, providing as much content as I can. Anyone else's going??? :) C u there!

So I couldn't resist and bought myself a MacBook Pro! It's my first week with my new toy and I'm really enjoying it. But I need to do something useful with it so I started to prepare it to be my new development platform, starting with Ruby/Rails + MySQL: Here is where the fun begins! After I installed both Rails and MySQL, I fired up a terminal an typed:

REXML, the XML library uses by many ruby apps, including rails, has a vulnerability that requires an immediate patch on whatever rails version you're using. Details and instructions on the official rails weblog, here. But basically, this is what you need to do: gem install rexml-expansion-fix Then, require rexml-expansion-fix in your rails's app environment.rb file.

So you found yourself in the need to override a method but still count on it's old behaviour? No problem! Override it with your new code, call super and.... Uh oh!! Suddenly this turned into a problem... Let me give some more context. I was testing Ferret (and the acts_as_ferret plugin) in a project to provide full text search capabilities to our models. One of the things the plugin does is to add a new method to ActiveRecord, called find_with_ferret.

Behold latin american railers! This year we will have the Rails Summit Latin America on October, 15th and 16th, in São Paulo, Brazil. It's by far the biggest Rails event we've ever had, including many of the speakers that were present at RailsConf. Fábio Akita is also one of the speakers and provides more details on his blog. If you're a assumed rails geek don't miss the opportunity to hear from the big names and to know a beautiful country like Brazil.

This week we started to test mod_rails in a couple of projects where I work on. One in production. Of course it's too early for any conclusions, but I just wanted to share a couple of problems you might find when the installer tries to compile the Apache module. In our case, and I believe it is the case of many servers out there, we have a custom Apache installation, what makes the installer not find it and/or not find the Apache Portable Runtime (APR) sometimes.

As some of you know I went to the European Ruby Conf in Prague, this year. The event was awesome and it's good to know they finally made available the majority of the slides, here. They also published Matz's keynote, and more videos from the conference are being edited right now, so stay tuned to their home page! Enjoy!

It's been some time since my last post but here I am! Where? In Spain, of course! Having a great time, I must say. I arrived last week in Madrid and the past 2 weeks before that I spent basically packing my stuff. There is still some paperwork going on but everything is flowing well. Besides this little feedback, I was reading this week's issue of the excellent series This Week In Ruby, from my friend Antonio Cangiano.

Passenger(mod_rails) has been released. The idea is to ease the pain on rails applications deployment. I tested myself and in less than five minutes I had my application working behind Apache! I'm not going to say much here besides the fact that it seems like a really good option for rails deployment and people have been talking about it already, including DHH. But I do recommend a read on the architecture overview document.

Update: Follow up link to this issue on JRuby's Jira, here As I told in my last post, it was time to give JRuby a serious try. So I took one of our rails projects at work and decided to migrate it to JRuby and see what happens. We heavily use the XML capabilities of DB2 and this was a huge problem. Every query would work just fine through the activerecord-jdbc-adapter - part of the JRuby Extras .

Most of last QCon's presentations are available for download here. Highlights to Ola Bini's on JRuby(pdf) and Randy Shoup's on eBay's architectural principles(pdf). And while we're talking about JRuby, it's impressive how it's becoming a recurrent and big subject. Fast. It had its own small space at big event like QCon and in the last Euruko in Prague, we had a presentation by the JRuby Core Developers Charles Nutter and Thomas Enebo.

This is quite funny. A friend, Perl addicted, is now learning Ruby. He really enjoys the language but made a interesting observation: Ruby is a language for lazy programmers! Well, I have to agree... You know, I love saving keystrokes and achieving more by writing less. And this is so true with Ruby. Let me give a really simple example, comparing with java - don't get me wrong... I love java, specially the platform, but it fits well here since I've always been a Java guy.

On friday I'll be heading Prague for the European RubyConf. Anyone is going? :) Almost 300 attendees already registered for the event. And a few very interesting people will be speaking there like Matz and DHH (this one, through skype). Besides that, the organization staff is scheduling 2 parties, friday and saturday, for the attendees. Networking comes to mind, doesn't it? I think it will be a great opportunity to meet interesting and bright people.

Today was the first day of the conference and it started with a tutorial about DSL's with Martin Fowler, Neal Ford and Rebecca Parsons. We also had as attendants Ola Bini, core developer of JRuby, and others. My expectations were pretty high and the presentation didn't let me down. I'll try to put here toghether my impressions and some notes I took while I was there. Marting Fowler started discussing what DSL's are and giving some examples that many of us use in our day to day Job.

I think I've been really lucky lately. In my new job I'm getting to work with many interesting things and OpenID is just one of them. We are investing high in Ruby on Rails and we have now a few internal applications in development stages. Our manager wanted the ability to let people log in to our rails applications(for now) using their OpenID accounts. It was a funny task, as I knew very little about OpenID.

[2008/04/30] Update: The ibm_db gem has been updated to support the new Rails 2.0 style migration. Now you can just use t.xml and it will work. Look here for more info. Thanks to Mario Briggs for pointing me to the update. --- In my new job we work with XML data natively stored on DB2. I have done some test with Rails and DB2 a few weeks ago and it's pretty interesting, specially the easiness that Rails deals with XML.

Following the Rails 2.0 hype, I've been playing around with it and decided to share a first impression: Scaffolding is gone! But wait, before you knock your head against the wall, let me tell you something: I lied :) Scaffolding is not really gone. It's just changed a bit. How can I tell? Well, as a good developer I thought: "I'll just create a scaffold with the new version and see what's different"

Well, we all know how hard, or at least cumbersome, it can be to set up a production environment to deploy your applications. Besides all the hardware stuff like storages, links, routers you are still left with a huge amount of software configuration to handle. This often includes configuring things like clusters, load balancing and services monitoring - Including notification of interested parts in case of any failure. Pieces of software you have to tie up and make them work together.

But hey, ruby lovers, you may have a better way to get this going! Released by ThoughtWorks, RubyWorks is, as quoted from their website, a production application stack for Ruby On Rails applications. I decided to give it a try and I really enjoyed it.

First of all I didn't want to mess with my actual configuration so I installed a new vm with Virtual Box. It has Ubuntu 7.10 on it, with 256MB of memory.

After installing RubyWorks - instructions on their website -, you get a new skeleton rails app up and running, being served by 4 mongrels that defaults to production environment! Impressed? There is more. A HAProxy is also set up in front of your mongrel servers acting as a load balancer.

Well, you probably want to monitor all that stuff huh? A monit web interface is waiting for your call on port 2812! It monitors all your mongrel servers - four by default - and your HAProxy, allowing you to measure CPU and Memory usage, among other things.

The coolest thing here is that all these softwares you would have to setup by hand are already working together, ready for production! Well, is it?

Going a little deeper, I deployed a database backed application to test this stack's performance.

I used Siege to stress the app and I am very happy with the results! I compared it with a single mongrel running on production env and no proxy at all.

It is worth mentioning that having 4 mongrels running took my vm to 77% of memory usage, while a single mongrel took it to 38%.

Although the title might look dramatic, it's pretty close to what I've been through. I have set up a Ubuntu 64 bits on my laptop last week to do some tests with Ruby and DB2. Oh man, it is not complicated, is it? It shouldn't be, actually. Too sad that I found this so late! It's a post from a friend, Antonio Cangiano, describing the most common problems you may find trying to set up this environment (Linux + Ruby + DB2).