Interpreted Languages in 10 Steps

1. Interpreted programming languages are languages which rely on another program (interpreter) to interpret code written by a programmer, into machine specific language.
2. Interpreted programming languages' objective is to provide development platform neutrality and shield programmers from specifics of the underlying operating system. History has proven that Operating System transparency is someone theoretical as nuances in interpreters' implementations and API, quite often prove migration projects to be as easy as fitting an elephant into a shoe box.
3. Interpreted languages are considered to be easier to learn and easier to develop on as programming language delegates responsibilities of more complex programming tasks such as memory utilization, memory recycling and underlying platform specifics, to the interpreter.
4. Some believed interpreted languages will eliminate memory leaks for good. In reality, memory leaks are thriving in systems programmed in interpreted languages.

5. Some believe that interpreted languages have allowed for generations of programmers lacking fundamental skills in software development.
6. No, C# is not a platform neutral interpreted language.
7. Yes, Java is a platform neutral interpreted language...until Java Run-time Environment (JRE), which is a fancy acronym for interpreter, commercial license agreement gets into picture.
8. Interpreted languages are usually slower than the big guns programming languages such as C++.
9. For the same reason mentioned in item 1 to 3 above, interpreted languages have accepted a very wide commercial adaptation.
10. A well written code in interpreted language can rock a lot though!

Congratulations, you are now a Subject Matter Expert in interpreted programming languages...sort of