Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
"Emmanuel Roldan" wrote: > I like this trick! I'm still very much a beginner in scripting. I've read > the O'Reilly Korn Shell book, the Kochan and Wood, and pored through Sed & > Awk. > How does one find/learn these nice ways? I'm sure the answer will be "over > time".... > > Also, is it worth a SA's while to keep on in the KSH scripting, or just jump > straight to PERL? > I am not all THAT fond of perl. I speak purely from the support side of the house though. For each of my customers who write perl code, and leave behind this legacy of scripts which depend on /usr/local/bin/perl being version 4.x and now of course, said developer has moved onto other stuff... it's just not a good use of my time to re-educate each new group of new hires on good perl scripting practices, and help them debug their inherited mess. Thus, my rule of thumb is this ... "if you want perl on one of my supported systems, you compile it, you install it in non-system directory, and you support it". It's no accident that Veritas does this for VCS... This would usually not apply for shell scripts, and thus I say YES ... Learning KSH and SH are still important skills to have. Not having slept for 48 hours, I'm sure that I'll read this tomorrow and wish I had just shut my yapper! - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |