That undefined method error on execution can really help. If you avoid it, then if the method name changes, or if you had typed the method name incorrectly, you may not find out about it quickly. Why would you use try? A few good reasons for using try might be: (1) you are absolutely sure the method name is correct and will not change, and/or (2) you might have used defined? to check that the method existed before attempting to call the method.
$ rails c ... 2.1.1 :001 > if ''.try(:incorrectly_named_method) 2.1.1 :002?> # assume method returned nil 2.1.1 :003 > end => nil 2.1.1 :004 > unless ''.incorrectly_named_method 2.1.1 :005?> # assume method returned nil 2.1.1 :006 > end NoMethodError: undefined method `incorrectly_named_method' for "":String from (irb):4 ... from bin/rails:4:in `require' from bin/rails:4:in `
Remember that Yoda said, "Try not. Do... or do not. There is no try."