<story><title>A Personal History of APL (1982)</title><url>https://ed-thelen.org/comp-hist/APL-hist.html</url></story><parent_chain></parent_chain><comment><author>jacquesm</author><text>The easiest way for non-APL programmers to begin to understand APL is to see what it hasn&amp;#x27;t got: boilerplate and loops. If you discard those from any other programming text you&amp;#x27;re left with the essence of what the code does. APL is only explicit about that essence, the rest is inferred by the interpreter. That&amp;#x27;s why it is so compact and that&amp;#x27;s why if you&amp;#x27;re used to step-by-step instructions with a ton of air in between you will initially find it hard to read. But that gets easier over time and before you know it you&amp;#x27;ll think of other languages as hopelessly verbose.</text></comment>
<story><title>A Personal History of APL (1982)</title><url>https://ed-thelen.org/comp-hist/APL-hist.html</url></story><parent_chain></parent_chain><comment><author>robomartin</author><text>I used APL professionally for about ten years.  One of the most interesting applications I worked on was the analysis of DNA sequencing data during the Human Genome project.</text></comment>