#clojure logs

2015-04-20

00:21TimMcsobel, nuwanda_: Yes, it provides escape-html, but that is literally the least it can do -- and it's not sufficient. It only takes one mistake for an entire site to be client-side compromised.
00:22TimMcI strongly recommend avoiding any HTML templating system that allows user data to become HTML by accident -- it has to be an opt-in thing on the part of the developer.
00:23TimMcunless you only have ninja vulcan robots who never make mistakes coding and maintaining your website, in which case go for it.
00:33saik0there a reason why iterate does not have a 1 arity like [f] (iterate f (f)) ?
00:49nuwanda_,(doc iterate)
00:49clojurebot"([f x]); Returns a lazy sequence of x, (f x), (f (f x)) etc. f must be free of side-effects"
00:50nuwanda_f needs to take an argument so that you can do (f (f (f ...)
01:28TEttingersaik0, if you want a lazyseq of calls to a 0-arg fn,
01:28TEttinger(doc repeatedly)
01:28clojurebot"([f] [n f]); Takes a function of no args, presumably with side effects, and returns an infinite (or length n if supplied) lazy sequence of calls to it"
01:28TEttinger(repeatedly #(rand-int 100))
01:28TEttinger,(repeatedly #(rand-int 100))
01:28clojurebot(4 87 5 8 10 ...)
02:46danielcomptonlein help gpg
02:46danielcompton<wall of text>
02:53danielcomptonfull credit to whoever wrote the documentation though, its very readable and understandable