This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-27
Channels
- # bangalore-clj (1)
- # beginners (27)
- # boot (16)
- # cider (14)
- # cljs-dev (94)
- # cljsrn (8)
- # clojure (229)
- # clojure-dev (5)
- # clojure-dusseldorf (6)
- # clojure-italy (8)
- # clojure-norway (8)
- # clojure-russia (22)
- # clojure-sanfrancisco (2)
- # clojure-spec (48)
- # clojure-uk (44)
- # clojurescript (47)
- # core-async (87)
- # cursive (43)
- # datascript (22)
- # datomic (20)
- # defnpodcast (5)
- # emacs (6)
- # hoplon (4)
- # jobs-rus (4)
- # keechma (2)
- # klipse (8)
- # leiningen (2)
- # luminus (2)
- # lumo (14)
- # om (38)
- # onyx (4)
- # overtone (3)
- # pedestal (41)
- # planck (72)
- # powderkeg (42)
- # proton (46)
- # protorepl (9)
- # reagent (9)
- # ring (47)
- # ring-swagger (5)
- # rum (7)
- # sql (22)
- # unrepl (1)
- # untangled (24)
- # vim (19)
- # yada (5)
i do generally prefer to order a source file top-down, it does annoy me slightly that clojure doesn’t let me choose to do that
I tend to have a big (comment
block at the bottom of my source file (or in the middle) where I put stuff for evaluating in the REPL - I rarely type into the REPL, because I want all my bits and pieces of stuff to stay with the code. And then when it comes to cleanup time I try to move the stuff in the (comment
block into tests 🙂
(parentheses deliberately left unclosed to mess with OCD types. It's ok, they won't read any of this because it's in a comment block)
@glenjamin I agree I would prefer to see high level fn's earlier and detailed ones later in the source file but I guess I've adapted to the reading a file from the bottom upwards in the same way I've adapted to reading s-expressions from the inside-out.
@korny, now the rest of their lives are in a comment block! They’ll never read anything again!!!
@peterwestmacott thank goodness you closed them... nothing worse than dangling parens!
I suspect the Cortisol levels of the people on this channel went up a bit while the parens weren't closed properly.
so @peterwestmacott provided a public health service there 🙂
you mean like this @thomas (take 5e9 (repeat \)))
?
don't think i'll get an SO from a lazy-seq @korny ?
i'd be better off mining ethercoin tho
@thomas it took about 6s for my iterm it print 1e6 \)
s... so i guess you'll be looking at a couple of hours to run given rough equivalences
I killed the process.... couldn't be arsed to kill the universe... even with a one liner it sounded too much like (hard) work 😉
"couldn't be arsed to kill the universe" - i fear you will make a hopeless evil genius @thomas
Evening friendly peeps. I know some of you work on some Clojure web Frameworks. Was hoping someone could remind me of which ones they are and what part of the stack they fulfill (e.g. yada, etc)?
We just use plain ol’ Ring, with Compojure for routing.
Frameworks mostly aren’t “The Clojure Way”.
@yogidevbear we're on yada, which is (roughly) about easily building HTTP compliant async services. it sits on top of netty and aleph, and behind a routing thingie like bidi, and gives you a schema with which to declare your HTTP resources. it looks after a bunch of hard to implement details like async multipart POST handling
other nifty features include resource schema coercion and swagger generation