This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-02
Channels
- # aleph (6)
- # beginners (37)
- # boot (415)
- # cider (17)
- # cljs-dev (79)
- # cljsjs (3)
- # cljsrn (18)
- # clojars (3)
- # clojure (34)
- # clojure-france (6)
- # clojure-italy (1)
- # clojure-korea (1)
- # clojure-russia (22)
- # clojure-spec (64)
- # clojure-uk (47)
- # clojurebridge (6)
- # clojurescript (61)
- # clojurex (1)
- # cloverage (11)
- # component (6)
- # cursive (73)
- # data-science (6)
- # datascript (4)
- # datomic (38)
- # editors (1)
- # emacs (4)
- # events (16)
- # funcool (5)
- # garden (3)
- # hoplon (17)
- # jobs (2)
- # klipse (74)
- # off-topic (3)
- # om (81)
- # onyx (35)
- # parinfer (4)
- # pedestal (1)
- # perun (20)
- # planck (9)
- # proton (1)
- # re-frame (17)
- # reagent (3)
- # ring-swagger (1)
- # rum (7)
- # untangled (63)
- # vim (8)
@micha: what is the rationale behind the newly-introduced --refers
option in boot-hoplon - why do we need another mechanism for magically injecting dependencies instead of simply mandating that jQuery be loaded from cljsjs as a :provided
dependency? i'm sure you have a good reason, but i'm curious to know what it is.
so if i want to log something i can use the logging macros that don't emit code for production
eliminating the extra step of :require the namespace etc means that i don't just use console log to quickly get some logging, which is what i would do if i didn't use --refers
@jumblerg also it's not a dependency issue, because jquery is always a dependency of hoplon, that hasn't changed
the hoplon.goog
namespace installs do!
and on!
multimethods that use google closure instead
:thumbsup: good summary!
a wild paul appears!
@alandipert heh; i haven't done web-dev for serious in awhile and I'm probably doing terrible things, but hoplon's workflow is just killer