From shell to system

Routine computer tasks and system programming require different tools, though I’m not entirely sure why.

Many people have thought about how inconsistent shells and system programming languages are and tried to unite them.

Wouldn’t it be nice to use one language for everything? But attempts to bring system languages down to the shell, or to push shell programming up to large programs, have not been very successful.

I learned Perl in college so I wouldn’t have to learn shell programming.

That’s what Perl was initially designed to be: an alternative to shell scripting.

Larry Wall called Perl a “distillation of Unix culture.

” Perl is the most disliked programming language according to Stack Overflow.

And yet I imagine many who complain about Perl gladly use the menagerie of quirky tools that Perl was created to unify.

Bash is popular while Perl is unpopular, and yet the quirkiest parts of Perl are precisely those it shares with bash.

I expect much of the frustration with Perl comes from using it as a language for writing larger programs.

Perl is very terse and expressive.

These features are assets for one-liners and individual use.

They are liabilities for large programs and team development.

Compared to a system programming language like Java, Perl is complex, inconsistent, and unsafe.

But compared to shell scripting, Perl is simple, consistent, and safe! Related posts Viability of unpopular programming languages Perl as a better grep Xonsh and shells in general.

Leave a Reply