CGI and application programmers certainly do, but sys admins might not.
This has been bugging me. Can't quite figure out why, but I figure responding will at least get it off my mind
I really think this all depends on what you view as a system admins role being. Also I suppoed what platform they are an admin for, but I think that is to a lesser extent. I have been a sysadmin for the last 4 years, and I have rarely used perl -e '' constructs, though I have worked on writing and maintaining perl scripts and apps on a daily basis. Any time it is as trivial as a perl -e '', I use system utilities to get the job done.
I have run just about the full gamut of possible system utilities short of creating a Tk/X based interface. Log parsers, automagic account and quota creation/deletion, wrappers around other system apps allowing for access restriction or business rule adherence, DB interfaces, network aware deamons launcing intersystem apps, yada, yada, yada. I was going to say I haven't built GUIs, but I suppose a browser is a GUI client. I certainly needed more than -e in order to do my job well. Matter of fact the only time I have played with -e, is usually due to a comment in a port or the CB.
use perl;
Everyone should spend some time pounding nails with their forehead for a while before they graduate to complicated stuff like hammers. - Dominus
| [reply] |
Certianly many sys admins get along without perl -e. In fact, I know one sys admin that hasn't learned much Perl because awk and sed does what he needs. I'm the opposite--I haven't learned awk or sed because perl -e does what I need for that problem domain (OTOH, I'm not technically employed as a sys admin, either). It's all a matter of what you're comfertable with.
----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer
: () { :|:& };:
Note: All code is untested, unless otherwise stated
| [reply]
[d/l]
[select] |
