As developers we are overwhelmed with the number of language choices made available to us. It wasn't so long ago that C and it's object oriented sibling C++ where the mainstay of any programmer. Now though we have languages which make certain tasks so easy and simple that we simply cannot afford to ignore them.

In this article we are going to look at the overall differences between Python, Perl and TCL. All formidable and worthy in their own right, but each one has been designed to suit a specific programming need.

1)– Perl is the most mature out of the three languages we are looking at in this article. It was originally designed for processing textual data, and it does so extremely well. Of course Perl has grown over time and can be used for a multitude of different programming scenarios.

JAVA SCRIPT TUTORIAL – THE ESSENTIAL ELEMENTS

If you are looking to increase your proficiency in programming, it can make a lot of sense to invest some time into learning how to use JavaScript, or taking a Java Script tutorial.  It is one of the most popular and powerful options available today for people to use in programming different parts of their websites.  It often finds use in headers, or in interactive features displayed on pages.  It allows you to execute many different functions, such as calculation, pulling data from forms, special graphical effects, customized selections, custom security protocol and password systems, and much more.  Here are some essential points to keep in mind:

·         Java vs. JavaScript – These two languages are not the same.  Java uses completely separate files for their headers and classes, and they need compilation prior to execution.  Java is used in the creation of applets for pages.  JavaScript is much easier and simpler to learn than regular Java, and Java Script tutorials are often significantly more accessible for the average user.

·         OOP – OOP, or object oriented programming, is a specific programming technique that simplifies complicated computer programming conceptual issues.  Essentially, it lets a programmer treat whole chunks of data (defined either by users, or by the system itself), and modify or access them in specific ways.  It does this by classifying different parts of the programming into Objects, Methods, and Properties, which will be discussed more in depth in the future, in other Java Script Tutorials.

Every programming language has a mechanism to allow the programmer to create variables which hold custom data entered in by either the coder themselves or by the user of the application.

Regardless of whether you’re new to programming or not, you will have used variables and you should understand that in javascript they can hold any value such as a number or a string of text.

There is also another type of variable called an Array. Now, depending on who you talk to, some will say an array is actually an object, while others say it is a variable. Neither one is wrong but for the sake of simplicity we’ll refer to it as a variable.

Now, arrays are special because they can hold multiple values as opposed to standard variables which can only hold a single value at one time. If you can, try and imagine that your computer’s memory is made up of thousands of little boxes, and each of those boxes has an address which javascript will use to retrieve the array values when needed.

The Zen of Python, by Tim Peters has been adopted by many as a model summary manual of python's philosophy.  Though these statements should be considered more as guideline and not mandatory rules, developers worldwide find the poem to be on a solid guiding ground.

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!