This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-10-28
Channels
- # aws (3)
- # beginners (14)
- # boot (222)
- # cider (9)
- # cljs-dev (14)
- # clojure (107)
- # clojure-chicago (1)
- # clojure-dev (31)
- # clojure-nl (1)
- # clojure-poland (3)
- # clojure-russia (44)
- # clojure-sg (13)
- # clojure-za (3)
- # clojurescript (81)
- # core-async (5)
- # core-logic (4)
- # cursive (3)
- # data-science (3)
- # datomic (13)
- # events (7)
- # ldnclj (6)
- # leiningen (1)
- # off-topic (4)
- # om (298)
- # re-frame (13)
- # ring-swagger (7)
- # yada (12)
See ya’ll at tonight’s meetup at Thoughtworks on Amoy St (I hope)!
@dilzio: it's a feather star... a type of Crinoid. Took us ages to figure out what it was too!
to all: I’m sorry I can’t make the meetup tonight. I’m traveling tomorrow and have a family obligation that needs attending to… best of luck to Lucas and Dapeng!
Slides from my talk today: https://docs.google.com/presentation/d/1WR_nCHwqNOP_lm1AFRCcTJkUbMEpviUTV6CGXHntI-k/pub?start=false&loop=false&delayms=3000
It devolved a bit into performance and “stuff I like”. Prefer simplicity over performance, but know that you can always get performance if you need it
http://www.onyxplatform.org/ is the distributed systems project I work on, if anyone is interested.
One thing to note when profiling Clojure code. Lazy sequences can obscure the actual source of costly computations. Sometimes you might want to add some "doall"s around your maps to simplify your call trees. There shouldn't be any performance hit unless you're actually using the laziness
I'm always happy to help out with exercism problems posted here, btw.