Matt Lawrence wrote in post #1104625:
> On Sat, 6 Apr 2013, D. Deryl Downey wrote:
>
>> Actually its not wrong. What it does is explicitly state which ruby
>> interpreter to use rather than using env to determine by finding the first
>> one in the path. His way in no way shape or form is wrong provided that
>> ruby actually lives there.
>
> As and operations person, I will point out that using
> #!/usr/bin/env ruby
> is a really, really bad idea for a production system.

or on the other hand, when #!/usr/bin/ruby is used in a gem, users gets 
problems because it does not work with rbenv, rvm or /usr/local builded 
ruby, env can be easier changed, even in a production system

-- 
Posted via http://www.ruby-forum.com/.