Earlier quoted context omitted.
If only they were advances rather than regressions. Far too much overhyped technology actually sets back progress by decades rather than advances it. Unfortunately, "the new student", never having learned the lessons of the past doesn't know any better and is condemned to repeat mistakes and reinvent and rediscover poor imitations of older technologies while calling them new.
Ok, learning to code and learning to design languages are different tasks. Those writing 'new' languages would be well-served to study the history and progression of languages. Those learning to code have enough on their plate, learning a mental model of computation and how to construct software for given tasks. History lessons are a case of 'too much information'
By learning the classics, especially those that are radically different from what you already know, you expand your mind and your sense of what is possible. It helps you get a different perspective on any given problem you may run in to, having seen radically different approaches to similar problems in the past. It puts another tool in your toolset and lets you select the best tool for the job.
Not that the above is not possible to get with exposure to hot new technologies, but whatever's hot in the market tends to be much more of a monoculture and popular due to being not too different from what most developers already know (Clojure and Scala being perfect examples).