| Full disclosure - I took 3 classes in Racket: Intro to CS, Programming Languages, and Compilers. > Racket is not a very popular language in teaching communities This list of schools with introductory Racket classes isn't accurate, because the author did not look beyond the naming of the courses on the Github page. My school was missed. > Students are unlikely to have had prior experience with Racket This is good because it means students from varying backgrounds of programming experience start from a level playing field. > Racket’s aesthetic beauty has limited relevance to CS1 Computer Science is first and foremost an ivory tower and students are (imo) better off being confronted with this fact up front. Software Engineering is probably better taught with a more practical language. > Students do not use Racket again later in their degree At my school the Programming Languages core curriculum all used Racket. A good percentage of students funneled into at least the first PL-core class as part of their requirements. The class was very popular. > Students do not like Racket Sorry, but I don't think we should base our decisions on what Intro students like/dislike. People hate leaving their comfort zone - that doesn't mean they shouldn't be pushed out of it. > The Design Recipe Is Not Well-Evidenced Valid criticisms. On the other hand, no evidence is presented that other languages are better. |
Although the article didn't cover it, I think it's important that in the industry, students will be able to find a job/internship that uses Python more than Racket. If both languages achieve the goal of introducing students to CS, why not use something that could benefit students more?