On Thu, Oct 05, 2000 at 04:53:00PM -0400, John Porter wrote: > May I point out that "the camel was designed by committee"*, too? The camel was certainly not, and this Camel isn't going to be either.[1] > Really, I'd like to see this Designed By Committee Considered Harmful > myth put to rest. It does seem to be pretty well bourne out in reality for a myth, doesn't it? (Incidentally, has anyone noticed that John Porter and I appear to have *completely* different opinions about *everything*?) [1] Unless you consider a committee of three plus editorial staff. -- Given an infinite amount of monkeys an infinite amount of time, an infinite amount of drafting supplies, and an infinite amount of crack, they'd come up with Downtown Chicago. -- David Jacoby, in the monastery
- Re: RFC 357 (v2) Perl should use XML for docu... Adam Turoff
- Re: RFC 357 (v2) Perl should use XML for documentation ins... John Porter
- Re: RFC 357 (v2) Perl should use XML for documentatio... Dan Sugalski
- Re: RFC 357 (v2) Perl should use XML for document... Nicholas Clark
- Re: RFC 357 (v2) Perl should use XML for docu... Dan Sugalski
- Re: RFC 357 (v2) Perl should use XML for ... Uri Guttman
- Re: RFC 357 (v2) Perl should use XML for document... Peter Scott
- Re: RFC 357 (v2) Perl should use XML for docu... Dan Sugalski
- Re: RFC 357 (v2) Perl should use XML for docu... Bart Lateur
- Re: RFC 357 (v2) Perl should use XML for docu... John Porter
- Re: RFC 357 (v2) Perl should use XML for ... Simon Cozens
- Re: RFC 357 (v2) Perl should use XML... Glenn Linderman
- Re: RFC 357 (v2) Perl should use XML... John Porter
- Re: RFC 357 (v2) Perl should use XML... Simon Cozens
- Re: RFC 357 (v2) Perl should use XML for documentatio... Adam Turoff