SICP translated to JavaScript
111–116 of 116 posts
Re: SICP translated to JavaScript
#112Re: SICP translated to JavaScript
#113Why so square? Translating SICP to Forth would be at least eclectic and truly creative gesture.
It explains and implements a Forth environment from scratch, initially in literate assembler code (yes, that exists) and then, once that's bootstrapped enough, in literate Forth that it runs using itself.
http://sage.math.washington.edu/home/wstein/www/home/wbhart/...
Re: SICP translated to JavaScript
#114Earlier quoted context omitted.
Sounds like that part of the system could be written once (in any language) and then encapsulated and treated as a local service... (analogous to using a local copy of SQLite if you need a db). Then you can use the "best tool for the job" on the client and-or server?
What if JS is the best tool for the job?
Re: SICP translated to JavaScript
#115"An invasion of armies can be resisted; an invasion of ideas cannot be resisted" - http://en.wikiversity.org/wiki/Victor_Hugo_quote This generation is going to be rewrite in Javascript/v8, everything that can be written in Javascript.
Re: SICP translated to JavaScript
#116Obvious objections - JS has no tail call elimination, no macros, and state-changing is managed with entirely different conventions in Scheme. Also the conceit of SICP (not really justified) is that they don't have to teach you syntax, because homoiconicity. Still, I think it's a worthy pursuit to try to bring the insights of this book to a wider audience. Side note: the navigation is really irritating. The back butto…
What syntax is there to teach?