Don’t disagree with a lot of the rest of your post, but this is a real, genuine virtue and ought not to be lightly dismissed.
I've taught Haskell at an university and almost none of the students ever found the model of computation natural. I think we humans simply find following a series of steps easier than reasoning in an abstract mathematical sense.
That being said, I absolutely see the value of the latter, and consider it a good thing that functional concepts are gaining popularity in imperative languages.
They seem naturally sequential and an imperative to me.
I can't imagine how a list of instructions would be clearer in haskell.
cook meat sauce = do
pan <- getPan
addTo pan meat
cookFor pan 10
addTo pan sauce
cookFor pan 3
food <- contents pan
pure foodAlthough written in an imperative style and thus superficially similar, the haskell differs in that it is referentially transparent.
I think that makes it objectively clearer, because it implies certain guarantees that nothing will surprise the reader.
It is not at all obvious that this is truly the case. If it was the case, why didn't humans intuitively develop mathematics from a computational foundation? It took centuries before we made the leap from mathematical abstractions to Turing machines, and the two are (in some great general sense) isomorphic.
So, you are right regarding the mindset of human philosophers, but that is not the sort of problems OP's students were tasked with solving.
Javascript is as easy to learn as any language, like understanding the syntax of a loop or an if-statement.
But to do anything practical at all, I'd say you quickly bump into a jungle of libraries you need for everything, and then it is just as complicated as any other language, or more. The javascript ecosystem is a nightmare.
Node makes this a lot harder, the simplest way to have interactivity is the readline library, and that requires you to understand functions, closures and the idea of a callback and why one is needed.
Then there's the "R way" of learning Python, in a Jupyter notebook, by stringing functions from Numpy, Pandas, Matplotlib and perhaps some other libraries in your field together, with no understanding of what a loop is, because you don't really need those for basic dataframe and tensor work.
Think of all the urgent iOS, Windows etc. patches which could be avoided if the software didn’t suffer from a number of classes of avoidable vulnerabilities.
> There is a reason that we write {...} rather than in C# or F#.
So are you arguing in favor of C#/F# here? you believe it was more suited for all of these cases? I hope not.
But again, if it's neither, then this comment seems like a out-of-context straw man.
Python's REPL isn't even any good, but it does at least exist which is more than you can say for most languages.
(And there's also the fact that it's crazy popular.)
Perhaps some of the old Lisp or Smalltalk environments could rival that, but no other modern language except Julia and R, which also have Jupyter support, come even close when repl ergonomics is concerned.
We write operating systems in C because it’s a thin veneer over assembly and coding in assembly is really hard. We use C++ instead of other languages because of its C interop.
Erlang is a really good fit for concurrency so that’s one of the few languages that’s used where it is for its technical merits.
Python is used for academic work solely because it’s easy to learn and easy to get started with so a lot of colleges used python to teach engineers/scientists programming. Python became the language of academia because that’s what the people in academia knew. If colleges had adopted Ruby or Lia for their Programming for non CS majors 101 classes instead, Lua or Ruby would be the language of academia.