[erlang-questions] Proposal: add lists:intersperse/2 and lists:intercalate/2

[Richard A. O'Keefe]

On 8/03/16 4:53 am, Garrett Smith wrote:
>
> For whatever reason FP pedantry is not a draw for me. When I need 
> inspiration I look to Python. Maybe that's the wrong direction and we 
> need to drive our community through more gates.

I don't know what "drive our community through more gates" means,
but copying Python is *definitely* the wrong direction.  Heck, even
*Python* (3) hasn't followed Python (2)  When it comes to cultural
compatibility with Erlang, Python is better than COBOL, PL/I, or RPG.
But that's about as far as I'd go.

For what it's worth, in Swift there is no 'join' function; instead there
are JoinGenerator and JoinSequence *types*.

Monads aren't pedantry: they're (an instance of) *power*.  If you can
view something as a Monad, then you get a range of useful operations
for free.  (And this applies to other things like Monoid as well.) It's
not, I think, unfair to say that
Haskell : Erlang :: Category Theory : Naive Set Theory.
I'm a set theory person myself; I have been trying for years to get
further than chapter 3 of any category theory textbook and failing.
(Not unlike the way I get the generalisation of vector spaces to
tensor algebras, but then Clifford algebras trigger math-acrophobia.)
I am very happy with Haskell as a typed functional language, but the
Haskell community does tend to push abstraction to levels where my
ears bleed.  But I understand why they are doing it, and it's not
pedantry:  it's the passionate pursuit of programming power from
precise analogies.  It's the entirely reasonable desire to take a
piece of code that might have worked in Lisp or Erlang and say
"WHY does it work? How can we KNOW before we call it that it's
going to work?"  It's the lazy programmer's wish to write something
just once crossed with the software engineer's wish that it should be
*safe* to do so.