This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-05-27
Channels
- # aleph (1)
- # beginners (48)
- # cider (34)
- # clojure (27)
- # clojure-dev (15)
- # clojure-uk (21)
- # clojurescript (27)
- # data-science (3)
- # datomic (10)
- # instaparse (30)
- # lumo (85)
- # off-topic (3)
- # perun (2)
- # portkey (24)
- # re-frame (13)
- # reagent (17)
- # ring (1)
- # shadow-cljs (77)
- # spacemacs (1)
- # test-check (3)
- # yada (4)
@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.
sorry that part of the docs is a worded a bit confusingly. It refers to using https://clojars.org/thheller/shadow-cljs. so the typical [thheller/shadow-cljs "2.3.27"]
is you are using lein
. see https://shadow-cljs.github.io/docs/UsersGuide.html#_installation
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?
@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
@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.
The trick is to use libraries that wrap javascript libraries, similar to how clojure wraps java libraries
Thanks, I’m not looking for an ide - I’m looking for a CLJS friendly rich text editor component to be used in a web page :)
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?)
@jrbrodie77 if you make a function call in a go block and you want to wait for something inside that function, you have to declare another go block inside the function, which will return a channel that you can wait on in the outer go block. this is a pretty easy to do with collections. https://clojure.org/guides/core_async_go#_unsupported_constructs_and_other_limitations_in_go_blocks