bun-neh
Students take to it pretty well when video lectures are available (my experience is that book only reverse classrooms don't work as well). It also generally leads to better retention, since more time is spent on hands-on experience.
Instructors also take it pretty well. Using an existing set of lecture materials reduces the preparation workload, especially in the first year teaching a course.
While you could probably catch a lot of cheaters this way, there is a possibility for a large false positive rate. If this is true then I would especially advise against deploying this type of software in a traditional university since the academic dishonesty policies can often cause significant and undue harm on an innocent student.
Perhaps you could say that basic statistical competency should be required for a college degree.
And besides, we segment and type the world all the time. Its a natural behavior to define an instance of a object and to reason about that object in isolation.
A lot of these points are really short-sighted. The reasoning behind eliminating code-as-data (note, not really self-modifying code) has more to do with efficiency than with clarity.
If you do accept the premise of the article then Javascript is not the only language for which it applies.
There is a package for lexical variables for those instances where stack shuffling is absolutely not the way to implement your algorithm. This page http://docs.factorcode.org/content/article-locals-examples.h... compares the stack shuffling vs lexical variable approaches. Oh, and those lexical variable have essentially no computational overhead.
I disagree that the tendency to factor a single function into many simpler ones exacerbates the understandability of a function. If done properly you get fantastically readable functions, such as this gem from https://github.com/JohnEarnest/Mako/blob/master/games/Deep/D... :
move-player fire waves bounce think draw-score spawn-crab storm
This snippet of a high level function is self describing.
1) Check to see if movement keyboard entry is pressed and move the player
2) check to see bomb keyboard entry is pressed and move an existing bomb
3) simulate the ocean waves
etc...Factoring gives you a chance to mitigate complexities in stack shuffling and allows you to build a semantically meaningful representation of your problem. Concatenative languages lend themselves to creating DSLs; every solution you write should be a small DSL for that particular problem or subproblem.