Interpreted programming languages are those that historically, and/or usually, use interpreters to interpret source code line by line, as they run, and output object (machine) code, often interactively, in a simple edit-debug cycle. This makes programming faster and more productive, but usually produces slower running programs. Almost all interpreted languages are garbage collected, use GC. Dynamic, and JIT (Just In Time) compilers are synonyms. They act much like interpreters, but compile (not interpret) source code as they run. They can turn interpreted languages into compiled ones, and can be written for any language. But the basic difference persists: while executing, at runtime, interpreted languages and dynamic compilers, make more decisions, do more computing, than compiled languages. On this page, languages are arranged in three groups and levels: 1) Top group: types or classes of languages. 2) Middle group: languages for which there are more than one instance of a language of this name/type, a language family. 3) Bottom group: specific languages which have their own directory category.
To this category, please submit only links on or related to interpreted programming languages.
Many programming languages use bytecodes, which are based on, and named after, bytes, 8-bit blocks of bits with which many computer users are familiar. Bytecoded languages use bytecodes as an interim form of information representation, an abstraction, between source code and object (machine) code, and use two conversion steps (transformations) when running: 1) source code is interpreted into bytecodes, 2) then bytecodes are run on an interpreter called a virtual machine (VM) which generates object code which is executed. This strategy gives two main benefits:

1) Compactness: bytecodes are a very compact representation.

2) High portability: source code can be written once and then run on any platform for which a VM exists. This inspired the Java slogan: Write once, run anywhere. Bytecode programs are usually run on, and executed by, bytecode interpreters, but sometimes they are compiled by bytecode compilers, or by dynamic or JIT (Just In Time) compilers, which are synonyms. These act much like interpreters, but compile (not interpret) source code as they run. They can turn interpreted languages into compiled ones, and can be written for any language. On this page, languages are arranged in two groups and levels: 1) Top group: languages for which there are more than one instance of a language of this name/type, a language family. 2) Bottom group: specific languages which have their own directory category.

This category points to directory categories for programming languages that are interpreted and functional.
This category points to directory categories for programming languages that are interpreted and multiparadigm: support, strongly, two or more programming paradigms.
This category points to directory categories for programming languages that are interpreted and object-oriented.
This category points to directory categories for programming languages that are interpreted and procedural, imperative.