6 ms·
One Reason That MIT Should Reinstate Scheme and 6.001 (2009)
- neonscribe 8y ago2009
- wltprgm 8y agoDidn't notice the date, thanks for the reminder
- chickenfries 8y agoThis seems to be less about Scheme and more about the author wanting to tell a cool story.
- taeric 8y agoThat is a true statement for the majority of rants in computer science.
- deleted 8y ago[deleted]
- gowld 8y ago> I feel that MIT is risking creating a new generation of idiots by getting rid of Scheme and SICP from their curriculum This is a confused rant about grammar. Scheme isn't the only language with grammar. Students should learn formal grammatical structure in English language class in high school, not programming class in college.
- JadeNB 8y ago> Students should learn formal grammatical structure in English language class in high school, not programming class in college. … but they don't. (There are also people—I'm among them—who found discussions of natural-language grammar dull, as belabouring too much a familiar point, until they saw the power that grammatical tools lent in the less familiar setting of formal specifications.)
- oflate 8y agoI think the compsci departments need a new course titled something like "Reading Code" where one learns to read any code fast and efficiently like they would a newspaper article or novel. Now that would be useful.
- farnsworth 8y agoCan that be taught in a classroom? There are various strategies and tricks one can use, but I think it's better to learn that skill "in the field" than out of a textbook.
- nostrademons 8y agoIt'd be interesting to see a course where you're given a large open-source project (say, Chromium or Linux or Postgres) and your task is to make & submit a small change in the codebase to implement some plain-language user request. The instructor would then walk you through how to download the project, read developer documentation, and build it; how to identify the relevant portion of the codebase, and everything else that your change might affect; how to match coding style & conventions; how to run tests; and how to submit a patch to the maintainers in a way that is likely to get accepted. Reading code is a real skillset, and being able to quickly grok & modify an unfamiliar codebase is a huge leg up in many jobs. Bonus points if the homework assignments for this course are real bug reports, so you end up contributing to open source for class credit.
- theparanoid 8y agoUniversities do have courses that require contributing to an Open Source project. I saw this when working on Servo a couple years ago. I was disappointed in the students. The average university student is not very motivated. If the course is an elective it's probably better (more motivated students).
- imglorp 8y agoOne might argue that sounds like software engineering, and that's mostly a separate activity from both programming and from computer science. Of course they overlap.
- deleted 8y ago[deleted]
- lgessler 8y agoA cool story no doubt, and this is a blog post, so the author should write whatever they please. But as someone who likes Lisp and genuinely does believe Lisp-family languages have underappreciated and incredibly powerful benefits, I was dismayed to see them leap to the conclusion that it was grappling with s-expressions that allowed him to solve this problem so well. Non sequitur, navel gazey paeans to Lisp are among the reasons why people have so much trouble taking the wild claims Lispers make seriously.
- euyyn 8y agoWhat benefit you think is underappreciated? It's a subjective point of view, but my experience is the contrary: that of Lisp-family languages being hyped to exhaustion.
- deleted 8y ago[deleted]
- nanomonkey 8y agoThe benefits of macros and code as data is under appreciated. It allows you to remove boilerplate code, and simplify your thought process, which makes for easier to read code. For example, in Clojure you can use macros to make a mini language that converts to HMTL at compile time: (defn index [] (html5 [:html [:head] [:body "the index-page"]])) Or similarly create your route handler on the back end that will serve up your pages: (defroutes app-routes (GET "/" [] (index)) (route/resources "/") ; if page is not found (route/not-found "Page not found")) Note how concise the language becomes, and this code will expand out to all of the necessary opening and closing tags or boiler plate code that makes your code safe and efficient. None of these syntax structures were previously in the language, they are instead created when needed for abstraction.
- AnimalMuppet 8y agoIt seems to me that, if you were to write that in Java, these would just be regular functions returning arrays of Strings or something similar. There would be a similar shortening of the source code. (It still wouldn't be as short, of course, but the same shortening would take place.) Am I missing something? What's the special macro-ness here that is different from regular functions?
- platz 8y ago> the Scheme programming language, in particular, can help in training non-programmers to think structurally in analyzing expressions in natural language Well if your making a course for non-programmers maybe.. I should think they would want to do the opposite
- _chris_ 8y agoIt's been over 10 years now. Is there a good post-mortem on the outcome of the switch away from 6.001 and Scheme?
- qwerty456127 8y agoWhatever, MIT dropping lisp looks unbelievably weird.
- throwaway487548 8y agoThere are actually more than one reason. I know at least two. 1. The classic Scheme based courses used to bootstrap an OO-DSL embedded in Scheme based on procedures and message-passing (you literally send a symbol by calling the object, which is a lambda, of course with an argument and get back a closure to run - a method). This is an invaluable experience to realize that there is absolutely nothing special about OOP and there is no magic. 2. There are still some gems (which leads to very real a-ha moments!) which cannot be taught in other languages. Here is one: (define partially (lambda (f . as) (lambda xs (apply f (append as xs))))) and then (define reverse (partially foldl (flip cons) '()))
- SkyMarshal 8y agoTLDR: Perhaps MIT should reinstate Scheme and 6.001, and get rid of Python and the new C1. Somehow I feel that MIT is risking creating a new generation of idiots by getting rid of Scheme and SICP from their curriculum just for the ostensible reason that the recursive style of programming does not reflect the way that programming is actually conducted in industry. Students do not learn programming just to program; learning programming also has important ramifications for the structural thought processes underlying other technical fields, even those that do not seem superficially related (such as patent translation), and it seems that watering down a core programming course for such ostensible reasons undermines the crucial patterns of thinking which are cross-applicable to such other technical fields as well. I wonder if Richard Stallman would have invented recursive copyleft law if he had never programmed in a lisp/scheme.
- bb88 8y agoI have observed the following in computer science departments. 1. They need students to justify their funding. If students stop taking their courses, they get funding decreases. 2. There are a lot of people that love SICP, and believe it should be the foundation for all computer science curriculum. 3. People pretty much agree it's important for computer science graduates, but the question is, should it be the first course? Are the concepts too hard, too soon? Does it weed too many students out too soon? 4. The industry at large is unconvinced about the benefits of Lisp dialects. They see high productivity gains with Java/C/C++/Python. And many students question why should they learn a language that doesn't advance their careers.
- deleted 8y ago[deleted]
- pjmlp 8y agoIn many countries, those that want to learn only industry relevant technologies go to a polytechnic school and not to an university. Universities are for learning to learn.
- AnimalMuppet 8y agoI disagree. Most universities have, for example, both a chemistry department and a chemical engineering department. They are different (but related) disciplines, but both belong at the university. In the same way, I think we need both "computer science" and "software engineering" - but they need to be different departments. They both belong at the university, though. (I'm not sure you go to a polytechnic school to learn chemical engineering.) The problem is, most universities try to teach a computer science degree to people who will work as software engineers (and therefore don't teach them as much software engineering as they should).
- pjmlp 8y agoDuring 5 years there is a lot of CS and Software Engineering to learn about. A solution to that is to have the Engineers college certify which university degrees are actually worthwhile to have engineering as part of their name, and crack down on misuses of the name by people that just had a bootcamp of some sort.