A caution about dates
The history of esoteric languages is informal. There is no official record, many early languages were shared in small groups, and creators often did not document when they finished something. This article therefore sticks to broad phases and avoids precise dates. If you need an exact year or name for a specific language, check that language’s own documentation.
Before the name existed
Computer scientists and hobbyists have been playing with unusual notations for about as long as there have been programming languages. Theoretical models such as the Turing machine, which uses a tape and a tiny set of rules, were never meant to be pleasant to program. They were designed to study what computation is. In that sense, minimal and awkward formalisms predate the hobby.
Humor also has a long history in programming. Spoof languages and satirical language descriptions circulated in computing circles well before the internet made them easy to share. Some of those were never implemented; they were written as jokes about the features of mainstream languages.
Small languages and a community of tinkerers
As personal computers and then the internet became widespread, people could easily publish a small interpreter and a short description. Several well known languages appeared in this period, including Befunge and Brainfuck, which are usually described as products of the 1990s, though exact details vary by source. Their appeal was clear. Brainfuck showed that a very small compiler could handle a complete language, while Befunge deliberately made program flow hard to follow by letting the instruction pointer move in several directions across a grid.
During this phase, many designers were chasing one of two ideas: make the smallest possible language, or make a language that is as hard to compile and read as possible. Both goals produced languages that are fun to discuss, and both inspired followers.
Variations and imitation
Once a few languages became known, others wrote variants and reskins. Some changed the commands but kept the semantics, while others added features or dimensions. The Funge family is an example: Funge-98 generalized the Befunge idea to a broader specification, and the many Funge variants beyond Funge-98 show how a single concept can branch.
This is a recurring pattern. A language with a clear core idea is easy to copy, extend or parody, so families of related languages form.
Wikis, contests and shared catalogs
Eventually the scattered enthusiasts built shared spaces: websites, mailing lists, forums and collaborative wikis where languages are cataloged. These spaces made it easy to find hundreds of designs, compare them, and see how languages relate. They also encouraged a more systematic culture of esolang challenges, such as writing a particular program in a restrictive language or competing to produce the shortest solution.
Over time, categories emerged: tape languages, stack languages, grid and two-dimensional languages, languages based on rewriting, and visual languages. The categories are informal, but they help newcomers navigate.
Esolangs and theory
A second thread runs through the history: a growing interest in the formal side. Because esolangs are small, they make convenient examples when discussing whether a language is Turing complete. Showing that a tiny language can simulate a Turing machine or similar system is a popular exercise. Questions about what can and cannot be decided about programs also come up often.
This does not mean every esolang designer is a theorist. Many are hobbyists who enjoy designing, implementing and sharing.
Where things stand
Today, esolangs remain a lively niche. New languages appear regularly, some as jokes and some as serious attempts to explore an idea about computation or notation. Programming puzzle sites, code golf communities and language-design enthusiasts all overlap with the scene.
The hobby has also found a place in teaching. Some instructors use small odd languages to illustrate how interpreters or machine models work, though this varies a lot by classroom.
Because the history is informal, you should treat any tidy timeline with some suspicion, including this one. The safest way to learn the story is to read the documentation of the languages you care about and follow how their authors describe their own motives.