This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-28
Channels
- # aleph (2)
- # beginners (25)
- # boot (12)
- # cider (73)
- # cljs-dev (3)
- # clojure (37)
- # clojure-dev (93)
- # clojure-germany (1)
- # clojure-italy (24)
- # clojure-nl (21)
- # clojure-russia (26)
- # clojure-spec (37)
- # clojure-uk (80)
- # clojure-za (1)
- # clojurescript (47)
- # cursive (4)
- # data-science (17)
- # datomic (69)
- # emacs (19)
- # events (7)
- # fulcro (41)
- # hoplon (14)
- # leiningen (2)
- # nrepl (4)
- # off-topic (253)
- # om (11)
- # portkey (2)
- # re-frame (11)
- # reagent (24)
- # ring-swagger (1)
- # rum (5)
- # schema (1)
- # shadow-cljs (106)
- # specter (2)
- # tools-deps (91)
If you know your way with Python and Numpy, a direct head-to head comparison will be a nice advertisment for Clojure. I simply don't have time to fiddle with Python, but will be delighted to do the Neanderthal part and the writeup!
@blueberry I’m not a python person either but maybe a script like this could help? https://gist.github.com/markus-beuckelmann/8bc25531b11158431a5b09a45abd6276
@gigasquid Maybe we could also check Neanderthal vs MXNet's backend?
I’ll keep that in mind - we don’t have any benchmarks yet for the Clojure MXNet package, but I have it as an item that needs contribution help
https://cwiki.apache.org/confluence/display/MXNET/Clojure+Package+Contribution+Needs
It would be better if the benchmark uses vanilla Java/Scala MXNet via interop, to avoid complaints that MXNet was crippled by Clojure's wrapper.