@jrbrodie77 (1) there's a channel called #re-frame (2) re-frame contains no macros, and doesn't use core.async.

I get this in emacs when i connect to my repl:

WARNING: CIDER's version (0.18.0-snapshot) does not match cider-nrepl's version (nil). Things will break!

how do i fix this?

i'm trying to get figwheel to work with cider, such that the repl i use in emacs is in the same state as the browser

got it!

:profiles
  {:dev
   {:dependencies [[binaryage/devtools "0.9.10"]
                   [figwheel-sidecar "0.5.16"]
                   [cider/piggieback "0.3.5"]
                   [org.clojure/tools.nrepl "0.2.13"]]
    :repl-options {:nrepl-middleware [cider.piggieback/wrap-cljs-repl]}
    :plugins      [[lein-figwheel "0.5.16"]]}
   :prod { }}

then cider-jack-in-clojurescript and it resolves correctly! When prompted for repl type, enter figwheel

The shadow-cljs docs recommend using a standalone .jar and point to http://clojars.org but I don’t see any links to a .jar on http://clojars.org nor any instructions as to how to configure the use of it.

javascripters, what benefits do you see in clojurescript vs just using javascript and immutablejs ?

You could argue that clojurescript is simpler, and followed more sensible decisions when the core libraries were developed. That could come off as a huge benefit.

That's a hard question to answer without seeming opinionated. It's easier to just recommend you try out both, and decide on whichever you prefer. Do you want to use a language which treats immutability as a first-class feature? Or do you want to use a library that offers it as a tack-on third-party library, but also offers a much bigger community with far more resources?

hard question indeed, and agree on using both for while

@benzap an important point is that if you want to interop with the JS ecosystem, "immutability as a first-class feature" causes issues too, just as using immutablejs

Any suggestions for a CLJS friendly wysiwyg editor?

@lockdown- I agree, the interop can be difficult to manage, since you're forced into dealing with mutability again. Which.. based on your point is kind of ironic.

@orestis that's a weird question

The trick is to use libraries that wrap javascript libraries, similar to how clojure wraps java libraries

@orestis http://nightcoders.net/

yes, wrappers are another story

To clarify, I’m looking for suggestions for a CLJS friendly rich text editing component.

I’ve seen a few contenders around the block, and I’m wondering if people might have experience integrating those in a CLJS app.

@justinlee I suspected that, but if I take the reframe stuff out of my functions, they work just fine. A clarification: the problem is when go blocks contain functions right? (The <! Is in a child function, parent contains go?)