Just as the use of sophisticated calculators is progress, but totally inappropriate for a class in basic arithmetic.
> Now we can think at a higher level, allowing us to quickly prototype new ideas.
First they must learn to think.
Nope. But doing it in assembly might... :)
Would you rather have brain surgery performed by a surgeon who learned his skill solely through telerobotics, one who actually cut a few heads open in his lifetime, or one who built the telerobotic system and cut a few heads open in his lifetime? I'll take the third.
IMO a good project for an algorithms class is to sort 20 GB of random floating point numbers. Having someone code a once off solution is of limited value as they will not recall what they did in a few months. However if you make them solve a problem and grade that. And then give them a harsh time constraint your students will learn something.
From what I have seen 95% of CS graduates don't understand how algorithms mesh with hardware. Sorting 20GB of data requires more RAM than they are going to have access to. So if they want to sort things quickly they are going to have to think about how access times alter an algorithms efficiency. So now we have an "easy" problem that exposes students to real world issues. Hand coding for a specific amount of L1 / L2 cache might have some value based on time constraints as is limiting the number of memory allocations by the OS etc.
IMO machine vision or other "hard" problems don't really help students at the introductory level as they use known methods by rote as apposed to rediscovering classic solutions to reasonable problems.