Posted by: Anonymous
[ip: 74.212.28.172]
on December 26, 2008 10:48 PM
Why not write shell scripts. To use a Perlism, TIMTOWTDI. The goal is usually getting a job done with the resources available.
Speaking for myself (I began using UNIX V3 while working for Western Electric in the early 70s), UNIX, the Bourne shell, sed, and awk allowed one to do a hell of a lot of useful work with amazingly little effort long before Perl came along. The shell, sed, awk combo (early 70s) preceeded Perl (late 80s) by about 15 years. Prior to Perl if you needed more speed you redid your shell work in C. When Larry Wall's Perl came along, IMHO, in the *NIX world it added a middle ground between shell and C - both Perl's execution speed and programming effort are greater than shell and less than C.
Having said all that, the reason I use Perl (in addition to shell, sed, awk, and their numerous *NIX provided friends) is CPAN - a truely awesome resource that has no real competition.
Learn about Linux
Download Linux
Get Linux help
Re: Why do people still write shell scripts?
Posted by: Anonymous [ip: 74.212.28.172] on December 26, 2008 10:48 PMSpeaking for myself (I began using UNIX V3 while working for Western Electric in the early 70s), UNIX, the Bourne shell, sed, and awk allowed one to do a hell of a lot of useful work with amazingly little effort long before Perl came along. The shell, sed, awk combo (early 70s) preceeded Perl (late 80s) by about 15 years. Prior to Perl if you needed more speed you redid your shell work in C. When Larry Wall's Perl came along, IMHO, in the *NIX world it added a middle ground between shell and C - both Perl's execution speed and programming effort are greater than shell and less than C.
Having said all that, the reason I use Perl (in addition to shell, sed, awk, and their numerous *NIX provided friends) is CPAN - a truely awesome resource that has no real competition.
#