Whatever you think of Ruby on Rails technically – even if you prefer
another language or development framework – you do have to admit that
Rails has gained huge acceptance in a short period of time. In this
CIO article, Hal F., author of The Ruby Way, explains what the
programming community did right, and how others can learn from it.
estherschindler wrote:
Whatever you think of Ruby on Rails technically – even if you prefer
another language or development framework – you do have to admit that
Rails has gained huge acceptance in a short period of time. In this
CIO article, Hal F., author of The Ruby Way, explains what the
programming community did right, and how others can learn from it.
Nice article.
One important point the author dances around is that many products owe
their
market share to relentless marketing, not their quality. This implies
that
a successful Free Software must be twice as good as a commercial one to
be
thought half as good in the trade press.
Fortunately this isn’t very difficult…
estherschindler wrote:
Whatever you think of Ruby on Rails technically – even if you prefer
another language or development framework – you do have to admit that
Rails has gained huge acceptance in a short period of time. In this
CIO article, Hal F., author of The Ruby Way, explains what the
programming community did right, and how others can learn from it.
Oops, I didn’t realize Esther had already posted this. Sorry
for double announcement.
Hal
On 7/26/07, Hal F. [email protected] wrote:
for double announcement.
Indeed you could have been more careful, now I have to read it
twice!!!
On 7/26/07, Phlip [email protected] wrote:
Robert D. wrote:
Oops, I didn’t realize Esther had already posted this. Sorry
for double announcement.Indeed you could have been more careful, now I have to read it twice!!!
Not very DRY, guys! (-;
Read it twice anyway, I just did, really
Robert D. wrote:
Oops, I didn’t realize Esther had already posted this. Sorry
for double announcement.
Indeed you could have been more careful, now I have to read it twice!!!
Not very DRY, guys! (-;
On 7/26/07, [email protected] [email protected] wrote:
Not very DRY, guys! (-;
Hal didn’t repeat himself – he repeated someone else
DROP. Don’t Repeat Other People
Hi –
On Fri, 27 Jul 2007, Phlip wrote:
Robert D. wrote:
Oops, I didn’t realize Esther had already posted this. Sorry
for double announcement.Indeed you could have been more careful, now I have to read it twice!!!
Not very DRY, guys! (-;
Hal didn’t repeat himself – he repeated someone else 
David
Hi –
On Fri, 27 Jul 2007, Robert D. wrote:
Indeed you could have been more careful, now I have to read it twice!!!
Not very DRY, guys! (-;
Hal didn’t repeat himself – he repeated someone else
DROP. Don’t Repeat Other People
DRAIN
Don’t Repeat Anything In No case
DRIP DRY
Don’t repeat it, period…
David
On 7/27/07, Gregory B. [email protected] wrote:
Indeed you could have been more careful, now I have to read it twice!!!
Not very DRY, guys! (-;
Hal didn’t repeat himself – he repeated someone else
DROP. Don’t Repeat Other People
DRAIN
Don’t Repeat Anything In No case
On 7/27/07, [email protected] [email protected] wrote:
Robert D. wrote:
DROP. Don’t Repeat Other People
DRAIN
Don’t Repeat Anything In No caseDRIP DRY
Don’t repeat it, period…
Hmm is this a subtle indication that maybe we are wasting a little bit
too much bandwith ;), I guess you are right.
RDDRRD
and out