Archive for June 16th, 2008
There has never been a statue erected to honor a critic.
- Ziglar, Zig
I couldn’t believe that someone would have the gall to actually go on record with grouses as trite as these against the creators of mod_rails … but they did
Basically here are their complaints about Phusion Passenger/mod_rails
- Their product has ‘Enterprise’ in the title
- They shouldn’t be up to version 2.0 already (yes … they actually said that)
- They release FREE products ‘late’ (late being an excruciating 2 weeks)
- They’d like for them them to be more ‘modest’ (like they haven’t heard of DHH)
- The marketing seems too slick and something ‘fishy’ is going on because they’re trying to make money with an Enterprise ready version of Passenger/mod_rails?!?!
- The ‘rails community’ will not embrace mod_rails because of these laughable quibbles … I guess these guys don’t count as part of the ‘rails community’ right?
ridiculous.
PS: Note that the original ‘rant’ appeared on Ruby flow, where it was rightly eviscerated
June 16th, 2008
The kickass developers over at Phusion have released an update to Phusion passenger (or as I prefer to call it … Apache mod rails).
You can see the list of original improvements here
It seems that this particular problem with mod-rails hanging after a few hours and taking down apache with it (I experienced this in an apache deployment that I tried personally … and its a bit scary) was part of the motivation behind the original mod_rails/Passenger Release Candidate.
Updating mod_rails to to 2.0 made all my problems go away (mod_rails also had some trouble interacting with the soap4r plugin), but this update has even more fixes.
I have a site running on mod_rails that was formerly served up using 3 mongrels in a cluster and it runs a bit faster than before, but deployment and application management is obviously MUCH less of a headache.
These guys are doing something for Ruby on Rails, that I don’t think many understand the implication of, but cannot be overstated. Big cheers to the guys at Phusion!
June 16th, 2008
Just got bitten by this one in Ruby on Rails.
If you use empty? to check a hash slice that doesn’t exist you get an error, instead of the behavior of nil? which simply reports that it is actually nil …
irb(main):004:0> test = {}
=> {}
irb(main):005:0> test = {'test' => '1'}
=> {"test"=>"1"}
irb(main):006:0> test
=> {"test"=>"1"}
irb(main):007:0> test.empty?
=> false
irb(main):008:0> test[test]
=> nil
irb(main):009:0> test['test']
=> “1″
irb(main):010:0> test['test'].empty?
=> false
irb(main):011:0> test['test'].nil?
=> false
irb(main):012:0> test['testx'].nil?
=> true
irb(main):013:0> test['testx'].empty?
NoMethodError: undefined method `empty?’ for nil:NilClass
from (irb):13
irb(main):014:0>
June 16th, 2008
