Well. I mean. I thought this was a good idea in 1986, but people told me the future was OO and Lisp had too many parentheses.

Also, many people will find functional programming difficult and just give up on it. But CS students should absolutely be introduced to functional (as well as OO, logic, dataflow) paradigms and purely applicative and point-free styles.

But CS programs don't even require compiler courses any more, so you can make it through a degree without ever learning parsing. CS programs are less about teaching kids CS and more about preparing them for jobs at FAANG companies so they have extra cash to donate to the alumni association or buy the alma mater a building.

But yeah... if you're interested in doing a good job in software, you should do enough Lisp (or erlang or haskell or whatever) to understand why other people rave about hygienic macros, metaprogramming and "the point free style." Bonus points if you can grok monads to the point you can explain it to someone else.

Oh god, all those functional examples w/ the Fibonacci function are malpractice. This was a big fight in the early 1980s because people who liked languages like Lisp and Logo were really pissed because Microsoft BASIC was everywhere.

The old way iterative we did it in BASIC or FORTRAN was better. Back in the 1980s the best "functional" examples involved drawing fractals, something that could drive you crazy if you tried to do it in BASIC.

If you are really smart you will use the closed form for Fibonacci which I think involves some really cool math

https://fabiandablander.com/r/Fibonacci.html

I have met so many young programmers who wander from job to job like itinerant martial artists looking for the true functional programming enlightenment and never finding it because... it doesn't exist. Functional and OO both started in the late 1970s and OO has prospered more because it is the key to writing simulations, graphical UIs, and many other kinds of programs. There are a lot of great ideas that came from the ML languages that are absolutely mainstream today, like algebraic types and pattern matching and you are seeing these being carefully weaved into languages like Java and Python right now. (Turns out those ideas from ML are really convenient for writing compilers!)

As @retrocryptid works around, you get real enlightenment from learning how compilers work, which is a bit advanced for the beginning programmer but you might be able to show people the power of interpreters early on. At my high school (that I attended part time in the 4th grade) we ran BASIC on an old PDP-8 and would draw "graphics" on the line printer with a simple DSL that came to a list of statements to the effect of "draw + 35 times, draw a space 15 times" which exposed us to some of the discipline involved in more complex programs. (Those old adventure games like Zork and the Scott Adams games always involved a specialized interpreter because without OO functionality it would be terrible to try writing that in BASIC, FORTRAN or Assembly.)

Start with "a monad is like a burrito" and you will lose even more people in CS 101 than they lose already.

no, beginning programmers need to learn negotiation, marketing and sales skills