tumba
Joined 17 years ago
Joined 17 years ago
Source: https://en.wikipedia.org/wiki/Expenditures_in_the_United_Sta...
Probably the best deep ground-level explanation of APL is Iverson’s paper “Notation as a tool of thought.” [0]
The bootstrapping explanation you describe sounds a lot like what Paul Graham did in “On Lisp” [1] and in a much more complex fashion, Queinnec in “Lisp in Small Pieces” [2], both highly recommended.
[0] https://www.jsoftware.com/papers/tot.htm
It will always be difficult to sustainably defeat recognition algorithms and I expect this to be an arms race along the same lines as other counter-surveillance techniques.
Gibson's suggestion that deeply coded and secret exceptions to mass surveillance might be used to protect state actors seems to me a plausible and concerning aspect of these developments.
https://web.archive.org/web/20120324074139/https://www.iata....
http://review.chicagobooth.edu/economics/2019/article/capita...
Indeed. Because both APL and Lisp began as languages for describing computational ideas, it stands to reason that they would be particularly fit relative to languages that evolved under other fitness criteria.
I was intrigued to not the opposition to APL mentioned in the article by Djikstra and others on the basis of a different mental model of computation.
In the context of setting the objectives for education in computer science for general students, I like the idea that the objectives are to (a) understand the limits and potential of computation and (b) achieve fluency in programming such that one can conceive of and describe computational processes for a wide range of tasks.
He explicitly suggests that fluency in using other people’s programs not be an objective. Perhaps this is a bit idealistic since most programming in the wild today consists of glueing together other people’s programs. But it seems like the right objective when possible—-in some ways it is a view of computer science as a liberal art.
> My advice is this: as you learn Common Lisp and look for
> libraries, try to suppress the voice in the back of your
> head that says “This project was last updated six years
> ago? That’s probably abandoned and broken.” The stability
> of Common Lisp means that sometimes libraries can just be
> done, not abandoned, so don’t dismiss them out of hand.
I have found this to be true in my own experience. The perception of stagnation is, however, a common initial objection to folks working in CL for the first time.
You can reach me at [email protected].