Skip to main content

I made a GIF!

Is PERL "quaint" ?

A developer asked me how I was scripting an integration task.  I replied PERL, then he smiled and said, "How quaint.".  There were platform limitations that made PERL or Java the only choices in that situation.

So I ask you, is PERL "quaint" ?
What language do you use for scripting and why?
What language would you use if you would/could/had-to change?

I prefer to recycle code rather than start fresh.  PERL and Java both being cross platform increases my chances to do that.  However I have always had Java version incompatibility issues as a user (not a developer) and the litany of security issues does not inspire confidence.  The latest TIOBE survey shows PERL and Java both holding steady, yet Java has a commanding lead at 17% to Perl's 2%. 

Using the native CLI is frequently the fastest means to an end.  BASH is fantastic for UNIX/Linux and even on Cygwin at times.  I use BASH extensively for UNIX/Linux administration tasks.  There are some PERL one-liners that I cannot live without.  I find myself using them from BASH scripts.  Windows command/cmd CLI is not adequate, however it is sometimes all you get.  MS PowerShell is a huge improvement and is an integral part of Windows 7 and Windows Server 2008 R2 now.  I only took a casual glance, but I understand advanced Microsoft Exchange and Active Directory administration essentially requires working PowerShell knowledge.  However, ActiveState PERL can easily be included in a self-extracting executable.  Even on Windows, PERL's portability proves its worth - especially when paired with the available WMI libraries.

C and its derivatives are not scripting languages, they are programming languages.  Any thing requiring a compile is too much effort.  I worked with PHP for web server forms and database integration and found it very nifty, even PERL-ish.  PHP is heavily geared towards web though, making finding one-liners and shell tasks sadly difficult to find.  A friend's learning/using LUA to manage SIP calls.  So LUA and Python are on my short list for personal development.  Python would likely be the more useful, but LUA sounds slick(er).  Looking forward to comments.

Refs:
"TIOBE Programming Community Index for January 2013" URL
http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html

"FOLDIT Wiki LUA Scripting" URL
http://foldit.wikia.com/wiki/Lua_Scripting

"Python » 3.3.0 Documentation » Tutorial" URL
http://docs.python.org/3/tutorial/

Comments

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error: Property "/general/LockCommand" does not exist on channel "xfce4-session". To fix this, additional configuration needed, but no hacks. First, verify xflock4 and xfconf-query are available. $ which xflock4 xfconf-query /bin/xflock4 /bin/xfconf-query Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar.  $ sudo yum install -y xlockmore-gtk i3lock Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings. $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type  string $ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string Test by running xflock4 from the command line or through the GUI.

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic