12 KiB
Programming Language
Programming language is an artificial formal (mathematically precise) language created in order to allow humans to relatively easily write algorithms for computers. It allows a human to very specifically and precisely tell computer what to do. Such language often tries to mimic human language (practically always English) so as to be somewhat close to humans but is also much MUCH simpler so that a computer can actually analyze it and understand it precisely, without ambiguity, so in the end it also partially looks like math expressions. A programming language can be seen as a middle ground between pure machine code (the computer's native language, very hard to handle by humans) and natural language (very hard to handle by computers).
For beginners: a programming language is actually much easier to learn than a foreign language, it will typically have fewer than 100 "words" to learn (out of which you'll mostly use like 10) and once you know one programming language, learning another becomes a breeze because they're all (usually) pretty similar in basic concepts. The hard part may be learning some of the concepts.
A programming language is distinct from a general computer language by its purpose to express algorithms and be used for creation of programs. This is to say that there are computer languages that are NOT programming languages (at least in the narrower sense), such as HTML, json and so on.
We divide programming languages into different groups. Perhaps the most common divisions is to two groups:
- compiled languages: Meant to be transformed by a compiler to a native (directly executable) binary program, i.e. before running the program we have to run it through the process of compilation into runnable form. These languages are typically more efficient but usually more difficult to program in, less flexible and the compiled programs are non-portable (can't just be copy-pasted to another computer with different architecture and expected to run; note that this doesn't mean compiled languages aren't portable, just that the compiled EXECUTABLE is not). These languages are usually lower level, use static and strong typing and more of manual memory management. Examples: C, C++, go, Haskell or Pascal.
- interpreted languages: Meant to be interpreted by an interpreter "on-the-go", i.e. what we write we can also immediately run. To run such program you need the interpreter of the language installed on your computer and this interpreter reads the source code as it is written and performs what it dictates (well, this is actually simplified as the interpreter normally also internally does a kind of quick "lightweight" compilation, but anyway...). These languages are generally less efficient (slower, use more RAM) but also more flexible, easier to program in and independent of platforms. These languages usually higher-level, use weak and dynamic typing and automatic memory management (garbage collection, ...). Examples: Python, Perl, JavaScript and BASH.
Sometimes the distinction here may not be completely clear, for example Python is normally considered an interpreted language but it can also be compiled into bytecode and even native code. Java is considered more of a compiled language but it doesn't compile to native code (it compiles to bytecode). C is traditionally a compiled language but there also exist C interpreters. Comun is meant to be both compiled and interpreted etc.
We can divide language in many more ways, for example based on their paradigm (roughly its core idea/model/"philosophy", e.g. impertaive, declarative, object-oriented, functional, logical, ...), purpose (general purpose, special purpose), computational power (turing complete or weaker), level of abstraction (high, low), typing (strong, weak, dynamic, static) or function evaluation (strict, lazy).
A computer language consists from two main parts:
- syntax: The grammar rules and words, i.e. how the language "looks", what expressions we are allowed to write in it. Syntax says which words can follow other words, if indentation has to follow some rules, how to insert comments in the source code, what format numbers can be written in, what kinds of names variables can have etc. Syntax is the surface part, it's often considered not as important or hard as semantics (e.g. syntax errors aren't really a big deal as the language processor immediately catches them and we correct them easily), but a good design of syntax is nevertheless still very important because that's what the programmer actually deals with a great amount of time.
- semantics: The meaning of what we write, i.e. semantics says what the syntax actually stands for. E.g. when syntax says it is possible to write
a / b, semantics says this means the mathematical operation of division and furthermore specifies what a and b can actually be, what happens if b is zero etc. Semantics is the deeper part as firstly it is more difficult to define and secondly it gives the language its features, its power to compute, usability, it can make the language robust or prone to errors, it can make it efficient or slow, easy and hard to compile, optimize etc.
Notable Languages
Here is a table of notable programming languages in chronological order (keep in mind a language usually has several versions/standards/implementations, this is just an overview).
| language | minimalist/good? | since | notes |
|---|---|---|---|
| "assembly" | yes but... | 1947? | NOT a single language, non-portable |
| Fortran | kind of | 1957 | similar to Pascal, compiled, fast, was used by scientists a lot |
| Lisp | yes | 1958 | elegant, KISS, functional, many variants (Common Lisp, Closure, ...) |
| Basic | kind of? | 1964 | mean both for beginners and professionals, probably efficient |
| Forth | yes | 1970 | stack-based, elegant, very KISS, interpreted and compiled |
| Pascal | kind of | 1970 | like "educational C", compiled, not so bad actually |
| C | kind of | 1972 | compiled, fastest, efficient, established, suckless, low-level, #1 lang. |
| Prolog | maybe? | 1972 | logic paradigm, hard to learn/use |
| Smalltalk | looks like yes? | 1972 | PURE OOP language, probably not as corrupt as C++/Java/... |
| C++ | no, bearable | 1982 | bastard child of C, only adds bloat (OOP), "games" |
| Ada | ??? | 1983 | { No idea about this, sorry. ~drummyfish } |
| Object Pascal | no | 1986 | Pascal with OOP (like what C++ is to C), i.e. only adds bloat |
| Objective-C | probably not | 1986 | kind of C with Smalltalk-style "pure" objects? |
| Perl | rather not | 1987 | interpreted, focused onstrings, has kinda cult following |
| Bash | well | 1989 | Unix scripting shell, very ugly syntax, not so elegant but bearable |
| Haskell | kind of | 1990 | functional, compiled, acceptable |
| Python | NO | 1991 | interpreted, huge bloat, slow, lightweight OOP, artificial obsolescence |
| Brainfuck | yes | 1993 | extremely minimal (8 commands), hard to use, esolang |
| Lua | kind of | 1993 | interpreted, mainly for scripting (used a lot in games) |
| Java | NO | 1995 | forced OOP, "platform independent" (bytecode), slow, bloat |
| JavaScript | NO | 1995 | interpreted, the web lang., bloated, classless OOP |
| PHP | no | 1995 | server-side web lang., OOP |
| Ruby | no | 1995 | similar to Python |
| C# | NO | 2000 | proprietary (yes it is), extremely bad lang. owned by Micro$oft, AVOID |
| D | no | 2001 | some expansion/rework of C++? OOP, generics etcetc. |
| Rust | NO! lol | 2006 | extremely bad, slow, freedom issues, toxic community, no standard, AVOID |
| Go | kind of | 2009 | "successor to C" but not well executed, bearable but rather avoid |
| LIL | yes | 2010? | not known too much but nice, "everything's a string" |
| comun | yes | 2022 | "official" LRS language, WIP, similar to Forth |
Interesting Programming Languages
Some programming languages may be interesting rather than directly useful, however they teach us a lot and may help us design good practically usable languages. In fact professional researches in theory of computation spend their whole lives dealing with such languages.
One such language is e.g. Unary, a programming language that only uses a single character while being Turing complete (i.e. having the highest possible "computing power", being able to express any program). All programs in Unary are just sequences of one character, differing only by their length (i.e. a program can also be seen just as a single natural number, the length of the sequence). We can do this because we can make an ordered list of all (infinitely many) possible programs in some simple programming language (such as a Turing machine or Brainfuck), i.e. assign each program its ordinal number (1st, 2nd, 3rd, ...) -- then to express a program we simply say the position of the program on the list.
There is a community around so called esoteric programming languages which takes great interest in such languages, from mere jokes (e.g. languages that look like cooking recipes or languages that can compute everything but can't output anything) to discussing semi-serious and serious, even philosophical and metaphysical questions. If you dare, kindly follow the rabbit hole.