To comp or not to comp

Re: Python and “one obvious way” – When I learned Python in 2013, that was definitely something that appealed to me. It was a huge relief after learning Ruby a year or two earlier and discovering that Ruby seems to intentionally support ten different ways to do absolutely everything :frowning:

For context, prior to picking up Clojure (in 2010), I’d been doing Scala and I had run into the “split brain” that is the Scala world of a) the Haskell-on-the-JVM crowd vs b) the better-Java crowd – two diametrically-opposed ways of doing anything. So Clojure seemed much more opinionated (which I liked) although it still – back then at least – seemed to have its more “functionally pure” crowd and its pragmatic, “just make stuff” crowd. And clearly my comp/partial monstrosity fell into the former camp. But I think a lot of that FP crowd left in those early years and with today’s pragmatic, maker-focused atmosphere, I hardly ever reach for partial and I’m much more sparing with comp too. I mean, who wants to read all that point-free code anyway?

3 Likes