Re: Too over complicated

Olek - You may find some of the convience functions you are missing in the Tupelo library. In particular: https://github.com/cloojure/tupelo#convenience-in-testing-seqs https://github.com/cloojure/tupelo#keeping-it-simple-with-not-nil Keeping It Simple with not-nil? Clojure has the build-in

Re: Too over complicated

On 19 June 2016 at 00:07, Olek wrote: > > Now lets talk about "difficulties" which I have found. > For example when we talk about removing element from collection. > > Why there is no one operation which could behave the same for set, vector, > list, string, and map?

Re: Too over complicated

The Clojure Cheatsheet can be very helpful if you are experiencing a shock of re-entry to clojure.core after a few years of relatively finite Javadoc pages of 10 methods per class. It is fun to chuckle at Alan Perlis' aphorism about 100 functions vs 10 each for 10 classes, but when you swing

Too over complicated

Hi! I've back to Clojure env. after 3 years of absence. I have started to code in my best language ever and was hit by some difficulties with the simplest things on earth I remember when I first dived into language and started coding in it. After 4 months of heavy doc/forum/irc usage I was