<P> In computer humor, a write - only language is a pejorative term for a programming language alleged to have syntax or semantics sufficiently dense and bizarre that any routine of significant size is too difficult to understand by other programmers and cannot be safely edited . Similarly, write - only code is source code so arcane, complex, or ill - structured that it cannot be reliably modified or even comprehended by anyone with the possible exception of the author . Write - only code is also referred to as line noise, suggesting that the code looks like spurious characters from signal noise in the communication line . In such a language it would be more difficult to read, understand, and modify existing source code than to start over and rewrite it from scratch . </P> <P> A more rarely used term is read - only language, which refers to systems with so many boundary conditions that the code can only be written through constant experimentation and not from first principles . The resulting code is perfectly readable by other programmers, but any attempt to duplicate it in another context will fail . AppleScript has been described as a read - only language . </P> <P> Languages that are often derided as write - only include APL, Dynamic debugging technique (DDT), Perl, Forth, Haskell, Text Editor and Corrector (TECO), Mathematica and regular expression syntax used in various languages . Attributes that these languages have in common include a large set of operators and a syntax which encourages, or at least permits, the writing of very dense code . Some also have syntaxes which are very different from other languages, and some use different characters sets . The code below for example is Conway's Game of Life as written in APL2: </P> <P> AppleScript has been described as a read - only language due to considerable implementation differences between different programs on the Macintosh platform . In theory, AppleScript is a simple language with considerable syntactic sugar that makes code easy to read and write . However, the core of the system, especially the system known as "chunking" and the objects it works on, has to be implemented within the third - party applications that support scripting . This support is not easy to add, and applications pick and choose which portions of the chunking system to implement . This leads to essentially random support within applications . </P>

How did perl gain a reputation for being a write-only language
find me the text answering this question