News for hackers. Stuff that matters.
Re:Why Racket? Why Lisp? by dragonwriter on Thursday August 21, 2014 @12:52PM (#8208301)
> What I mean is not the trivial "nand is turing complete" sense, which I agree is harmful and silly, but full eval capabilities.

The two are equivalent (provided that the target language that can be evaluated is itself turing complete) -- that's rather the nature of turing completeness. If you have the former, you can make the latter with it and nothing else; if you have the latter, you necessarily also have the former.

Re:Why Racket? Why Lisp? by wes-exp on Thursday August 21, 2014 @01:12PM (#8208411)
Yes, it was a poor choice of terms. To be clear, eval isn't equivalent except within the narrow theoretical notion of turing completeness: it can do I/O, for instance file I/O. And it accepts high-level language code directly which is very important in a practical sense compared to, say, accepting nand instructions only.