This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-06
Channels
- # admin-announcements (6)
- # beginners (147)
- # boot (9)
- # braveandtrue (5)
- # cider (11)
- # cljsjs (1)
- # cljsrn (4)
- # clojure (82)
- # clojure-greece (9)
- # clojure-poland (9)
- # clojure-russia (288)
- # clojure-taiwan (2)
- # clojure-uk (73)
- # clojurescript (123)
- # consulting (3)
- # cursive (26)
- # datascript (4)
- # datomic (32)
- # dirac (56)
- # emacs (11)
- # flambo (2)
- # hoplon (425)
- # jobs-rus (1)
- # lein-figwheel (3)
- # leiningen (16)
- # luminus (42)
- # mount (7)
- # om (1)
- # om-next (2)
- # onyx (8)
- # other-languages (146)
- # quil (3)
- # re-frame (17)
- # reagent (6)
- # spacemacs (2)
- # uncomplicate (8)
- # untangled (71)
- # vim (2)
- # yada (49)
wouldn't that be a heavyweight solution? Neanderthal is a library - it should work in any environment you put it.
@aaelony atlas builds in that container wouldn't be optimized for the hardware architecture the container is running on.
yeah, it's definitely a tension between ease of install and use versus performance (which is the main point). I'm in agreement now.
was just a crazy thought to think that, well, if it's only tested and seamless on one platform right now, just make a docker container for that platform. But from a performance context, it defeats the purpose.
From a user adoption library perspective though, it might make sense, but not if benchmarking is the goal