His other book was PLAI which was pretty cool: http://cs.brown.edu/courses/cs173/2012/book/ I worked through it for a class, and I distinctly remember a moment where I thought "what the fuck - did I just write a working type inferencer?". It has a great way of simplifying things to the point where adding a complex new language feature isn't a distant theoretical proposition, it seems like a simple and straightforward…
Programming and Programming Languages
11–20 of 68 posts
Re: Programming and Programming Languages
#12Earlier quoted context omitted.
More like a spiritual successor to HtDP, which is somewhat opposed to the SICP philosophy, even though both use Scheme variants: http://cs.brown.edu/~sk/Publications/Papers/Published/fffk-h...
How is HtDP opposed to the SICP philosophy? From my reading both come off as espousing the more or less same ideas for building programs.
Re: Programming and Programming Languages
#13Earlier quoted context omitted.
More like a spiritual successor to HtDP, which is somewhat opposed to the SICP philosophy, even though both use Scheme variants: http://cs.brown.edu/~sk/Publications/Papers/Published/fffk-h...
I am curious what evidence there is that SICP is responsible for "[many introductory] courses quickly disappeared again due to shortcomings of the book and the whimsies of Scheme."
Re: Programming and Programming Languages
#14Earlier quoted context omitted.
More like a spiritual successor to HtDP, which is somewhat opposed to the SICP philosophy, even though both use Scheme variants: http://cs.brown.edu/~sk/Publications/Papers/Published/fffk-h...
Interesting... It seems to me that FP is having quite a renaissance recently, which could limit the relevance of that paper's contentions today. I'm also seeing quite a backlash against OOP and especially OOP as the One True Paradigm that it was pushed as in throughout the 00s - this can be seen not only in FP language growth but also in the design of other new languages like Go that lack many OOP features. Honestly,…
Re: Programming and Programming Languages
#15At first glance this book appears in many ways to be a spiritual successor to SICP... does this hold up for anyone who has read it more throughly?
Re: Programming and Programming Languages
#16Re: Programming and Programming Languages
#17Earlier quoted context omitted.
I am curious what evidence there is that SICP is responsible for "[many introductory] courses quickly disappeared again due to shortcomings of the book and the whimsies of Scheme."
It's a comment based on our view of the historical record, having been present during the rise and fall of SICP. It is not a formal evidence-based claim.
It seemed that the money was heavily pushing Java and that most curriculum immediately jumped to where they thought future money was. Sometimes they would back off and try to get back to a more theoretical or instruction based methodology, but would always hedge with a language that was seen as friendly to industry.
Re: Programming and Programming Languages
#18@shriramkmurthi may I know what license PLAI and PAPL are released under? I couldn't find it on the linked page.
At any rate, I'm committed to having a full copy of the book available for free to all, as is also true of HtDP (we were one of the pioneers in this space) and PLAI (which has even more free/commercial options than HtDP).
You may assume at least a CC BY-NC-ND, which lets typical users have at it right away.
Re: Programming and Programming Languages
#19Earlier quoted context omitted.
I am curious what evidence there is that SICP is responsible for "[many introductory] courses quickly disappeared again due to shortcomings of the book and the whimsies of Scheme."
It's a comment based on our view of the historical record, having been present during the rise and fall of SICP. It is not a formal evidence-based claim.
Re: Programming and Programming Languages
#20His other book was PLAI which was pretty cool: http://cs.brown.edu/courses/cs173/2012/book/ I worked through it for a class, and I distinctly remember a moment where I thought "what the fuck - did I just write a working type inferencer?". It has a great way of simplifying things to the point where adding a complex new language feature isn't a distant theoretical proposition, it seems like a simple and straightforward…