I had the need to write some Perl code recently which forced me to pull
out Learning Perl from the bookshelf. Larry Wall wrote a very
entertaining forward that takes issue with some of these principles.
http://portal.acm.org/citation.cfm?id=572875
Definitely worth reading and provides some
Lloyd Kvam writes:
I had the need to write some Perl code recently which forced me to pull
out Learning Perl from the bookshelf. Larry Wall wrote a very
entertaining forward that takes issue with some of these principles.
I dunno. I think that if you were to ask lwall the specific question
From: kevin_d_cl...@comcast.net (Kevin D. Clark)
Date: 09 Mar 2009 12:29:19 -0400
I think the need for AWK/Sed crib sheets argues that the tools we've
traditionally used for piping text might benefit from some fresh
insights.
I use crib sheets for various things, actually. My tiny
On Mon, 2009-03-09 at 12:29 -0400, Kevin D. Clark wrote:
I would argue that the Unix Philosophy has room in it for both patch
and Perl. patch makes it in easily, whereas Perl knocked down one
of the walls but many people don't mind because of its usefulness. If
something isn't useful it is
David Montenegro writes:
Reliance on crib sheets can be mitigated by practice. Using a
language on a regular basis certainly makes remembering it easier.
cough, cough In my particular case, I would say that lack of
practice is not the problem.
--kevin
--
GnuPG ID: B280F24E
jk...@kinz.org writes:
The example of GNOME choosing to have non-human-editable
configuration files is but a single instance in this waterfall of
movement.
GNOME forced me to abandoned it when I was *required* to install a
sound library because of a dependancy upon it by the printing
From _The UNIX Philosophy_ by Mike Gancarz (a member of original X
window system team):
Two stories about Mike:
Story 1:
Mike was a young engineer, new to Digital's X programming group. We had
shipped a version of the X Window system in ULTRIX based on X Version
10.3, and were now gearing up
On Mon, Feb 09, 2009 at 10:00:06PM -0500, Ben Scott wrote:
Write programs that do one thing and do it well. Write programs to
work together. Write programs that handle text streams, because that
is a universal interface. -- Doug McIlroy (inventor of Unix pipes;
currently Adjunct Professor
Look at its wirth instead.
Ahhh, Niklaus Wirth...another giant!
md
--
Jon maddog Hall
Executive Director Linux International(R)
email: mad...@li.org 80 Amherst St.
Voice: +1.603.672.4557 Amherst, N.H. 03031-3032 U.S.A.
WWW: http://www.li.org
Board Member: Uniforum
From: jk...@kinz.org
Date: Tue, 10 Feb 2009 10:12:02 -0500
From _The UNIX Philosophy_ by Mike Gancarz (a member of original X
window system team):
Universal:
1. Small is beautiful.
2. Make each program do one thing well.
3. Build a prototype as soon as possible.
4.
Write programs that do one thing and do it well. Write programs to
work together. Write programs that handle text streams, because that
is a universal interface. -- Doug McIlroy (inventor of Unix pipes;
currently Adjunct Professor at NH's own Dartmouth College)
From _The UNIX Philosophy_ by
11 matches
Mail list logo
