MIT 已经不教 SICP 了

是好消息还是坏消息呢?
:)

我也没看完

一直计划看看的，一直没有看

这都那年的事了，早换 python 了

和楼主引用的一样。我觉得现在这种快速的，通过组装组件让程序跑起来，不在意里面到底运行了些什么的做法，应该算是一种倒退吧？这一段是读起来最伤心的了。

Today, this is no longer the case. Sussman pointed out that engineers now routinely write code for complicated hardware that they don ’ t fully understand (and often can ’ t understand because of trade secrecy.) The same is true at the software level, since programming environments consist of gigantic libraries with enormous functionality. According to Sussman, his students spend most of their time reading manuals for these libraries to figure out how to stitch them together to get a job done. He said that programming today is “ More like science. You grab this piece of library and you poke at it. You write programs that poke it and see what it does. And you say, ‘ Can I tweak it to do the thing I want?'”. The “ analysis-by-synthesis ” view of SICP — where you build a larger system out of smaller, simple parts — became irrelevant. Nowadays, we do programming by poking.

太功利了

早就不教了。。
都是面向文档编程了

才看了一章。。

meh 学校的入门课教材用 sicp 但是从来没人看的说
cs61a.org

都不知道这是啥东西

那该看什么？...
做啥都要翻文档确实挺烦。

这种书作为基础“入门教程”确实过时了

作为中科大少年班的同学很有必要

但是代码到了一定规模以后，就算调用了很多第三方库，自己的代码也需要良好的组织与合理的抽象。 SICP 只是不适合作为入门了而已

证明程序的复杂度和抽象程序比以前更高了，从底层一步步构建已经太累了，都用现成的轮子。提高造轮子的人和使用轮子的人的分工程度，对于一直甘于只用轮子不造轮子的人，确实作用不大了