Linked by Shlomi Fish on Sat 16th Oct 2004 07:28 UTC
General Development The purpose of this essay is to explain why I believe Perl 6, the way it currently seems to progress, is the wrong thing at the wrong time, and why I predict (with all the expected caveats of predicting something) that it won't be successful. I will also suggest a better alternative for the future of Perl which makes more sense at this point.
Permalink for comment
To read all comments associated with this story, please click here.
Is "scripting" inherent to the language?
by Chris on Sun 17th Oct 2004 04:11 UTC

No.

Scripting is a subcategory of programming, but you can't extend that relationship to say "scripting languages" are a subset of "programming languages".

It's all about the use of a language.

For insance, we commonly consider bash a scripting language because it is most frequently used to control (or "script") the actions of other applications. If we were to write a shell script, the majority of the logic should be taking place transparently in those other applications.

This of course is where we get the perception that anything that allows a relatively small amount to get a lot of things done comes from.

If we want to unzip a file in the course of accomplishing a larger computing task, we don't write a huge C program to do all of that work. Instead we write a tiny shell script which lets something like gunzip do all of the heavy lifting.

Of course, then we get into the realm of languages that simply have huge libraries and the difference between "scripting" and "programming" becomes more ambiguous.

Are we writing a "program", or just scripting the underlying libraries? After all, we're writing ever more concise programs which hand off ever more of the heavy logic to some library.