Just as a thought experiment: The FTP had a landslide support on the libraries list.
How would it have fared on a Haskell-Edu list?
Judging by the list of changes at https://wiki.haskell.org/Foldable_Traversable_In_Prelude
the changes were mostly some extra classes (Monoid, Foldable, Traverseable) showing up
in Prelude and a bunch of type changes to functions:
... [x] ... changing to (Foldable t) => ... t x ...
... [x] ... changing to (Traverseable t) => ... t x ...
This is actually quite an interesting change.
Using the same names *consistently* across a wide range of types
makes programs easier to write and easier to read.
>From an educational point of view, you can't say
"We didn't need the Prelude to write `all` for us.
We could have written
all p (x:xs) = p x && all p xs
all _ [] = True
"
any more because that has the wrong (old, list-specific) type.
You *can* say
"We could have written
all = foldr True (&&)
"
So you lose a lesson that comes somewhere near the beginning,
when you are still trying to get across the idea of higher order
functions and lazy evaluation, and gain a lesson that comes
much later, about the power that typeclasses add to composition.
Come to think of it, you could use this to motivate typeclasses.
I think you could build *just as good* an introductory Haskell
course on the post-FTP libraries as you could on the pre-FTP
libraries, but it would be a *different* course.