%% > That’s what I love about Ruby’s OO model. Complain less, get more
%% > work done.
%% This seems like it leads to each person reinventing the same new
%% methods (or
%% hacks), but not sharing them, rather than enhancing the public code base.
Good point, I wasn’t trying to comment on the virtues of open source
development, though. Specifically I was just trying to coo about Ruby’s
dynamicity. The lack of a commonly accepted “redirect” method in CGI is not
a showstopper and very little code is needed to remedy the situation, was my
only point. And you don’t have to wait till the community adopts your fix,
I’ll add to that, or mess with the original public codebase to do it, I’ll
add to that.
%% I don’t understand why an observation on the lack of a built-in
%% way to emit
%% a common HTTP header is considered a complaint.
OK, strike that wording and change “complain” to “despair” or even, more
innocuously, “frown disapprovingly”. My point was merely that unlike in
other languages, where builtins are hard and fast and you need to wait till
the next release for your feature to appear (maybe), you can fairly easily
modify the behavior of even the most fundamental objects in Ruby. And as
long as you modifying these objects in your application code or libraries,
you aren’t going to muck up the public codebase, and if a fix or enhancement
comes along, you shouldn’t have to change much at all if anything but a line
or two in your code to take advantage of the new stuff.
I apologize for the wording; I did not mean it the way it came out.