This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-03
Channels
- # arachne (1)
- # beginners (71)
- # boot (14)
- # cider (17)
- # cljs-dev (3)
- # clojure (169)
- # clojure-gamedev (35)
- # clojure-greece (1)
- # clojure-russia (30)
- # clojure-spec (3)
- # clojurescript (16)
- # core-async (2)
- # cursive (1)
- # datomic (3)
- # dirac (1)
- # hoplon (95)
- # off-topic (10)
- # onyx (1)
- # parinfer (1)
- # pedestal (2)
- # re-frame (2)
- # reagent (2)
- # untangled (1)
fyi I just tried Tonsky's Rum react library with Javelin. Code became much more declarative. Thank you all
@myguidingstar: do you have an example to look at?
sure. I'm making a simple gist
hmm, too bad. There's no service like codepen for Clojurescript that allows us to specify arbitrary build dependencies
or at least popular libraries with any version
@micha here you are https://gist.github.com/myguidingstar/bfd0d94f9b1541b944667b0f7cfc46f7
among the Reactjs hype in Cljs community, Reagent is more famous 🙂
noteworthy use of the term toolkit rather than framework from tim fox to describe vertx:
Another important point is that Vert.x is toolkit, not a container or "framework". That means you can use it within your existing application to give it the Vert.x super powers. For example you can use it within your Spring application, and many users do.
perhaps hoplon should adopt this sort positioning statement, esp in light of the previous conversation.javelin, castra, hoplon, etc. are designed to work together, but can all be used independently of each other in the some sense.
i def a symbol, p. i tell p to do a thing. hoplon page puts a gun to p and forces it to do something else.
i think the key difference between the page macro vs reserved words or even an implicit :refer :all
is that it shadowed me instead of the other way around.
(def comp "foo")
WARNING: comp already refers to: #'clojure.core/comp in namespace: boot.user, being replaced by: #'boot.user/comp
#'boot.user/comp
boot.user=> comp
"foo”
(def comp "foo")
foo
comp
function cljs$core$comp(var_args){ var args9221 = []; var len__6905__auto___9248 = arguments.length; var i__6906__auto___9249 = (0); while(true){ if((i__6906__auto___9249 < len__6905__auto___9248)){ args9221.push((arguments[i__6906__auto___9249])); var G__9250 = (i__6906__auto___9249 + (1)); i__6906__auto___9249 = G__9250; continue; } else { } break; } var G__9227 = args9221.length; switch (G__9227) { case 0: return cljs.core.comp.cljs$core$IFn$_invoke$arity$0(); break; case 1: return cljs.core.comp.cljs$core$IFn$_invoke$arity$1((arguments[(0)])); break; case 2: return cljs.core.comp.cljs$core$IFn$_invoke$arity$2((arguments[(0)]),(arguments[(1)])); break; case 3: return cljs.core.comp.cljs$core$IFn$_invoke$arity$3((arguments[(0)]),(arguments[(1)]),(arguments[(2)])); break; default: var argseq__6924__auto__ = (new cljs.core.IndexedSeq(args9221.slice((3)),(0),null)); return cljs.core.comp.cljs$core$IFn$_invoke$arity$variadic((arguments[(0)]),(arguments[(1)]),(arguments[(2)]),argseq__6924__auto__); } }
the cljs repl provides a limited extension so you can do things like require
or see metadat on vars etc
i suspect this will also make certain individuals who like to use the more feature-laden development tools happy as well.
like my index.cljs.hl file usally doesn't have any real logic in it, it just assembles things from other namespaces
i was just hearing from some folks using ides that were made uphappy by the page
up top instead of the ns
declaration.
@micha seems like a positive change the ns thing