Why MIT Switched from Scheme to Python (2009)

Re:Why MIT Switched from Scheme to Python (2009) by wffurr on Friday April 21, 2017 @04:14PM (#14169039)

The sheer amount of nonsensical boilerplate required in any Java program, even trivial ones, makes it a terrible language for teaching Computer Science.

Think about trying to teach the meaning of "public class Foo { public static void main(String[] args) { ... }}" to a complete novice. Class-based design, inheritance, visibility, return types, arrays, etc. all right off the bat. It's too much.

Scheme and Python both are much better choices for this alone.

[ Parent | on HN ]

Re:Why MIT Switched from Scheme to Python (2009) by jksmith on Friday April 21, 2017 @06:14PM (#14169850)

Some snarky drift: Then post-college commercial reality sets in, where using mind numbing boilerplate supported by frameworks and heavy ides (as opposed to libraries, custom or otherwise, and an editor), is SOP. Join the programming masses and literally think inside the box(es). So why did you go to college now?

[ Parent | on HN ]

Re:Why MIT Switched from Scheme to Python (2009) by int_19h on Saturday April 22, 2017 @02:50AM (#14171416)

So that you can realize that you're inside a box, and leave it on those few opportunities that present themselves (and, perhaps, specifically seek out such opportunities).

[ Parent | on HN ]