@lwhorton You can certainly write macros that expand to any code you'd like including code that has qualified keys and symbols. The trick is whether this expanded code can then be compiled.

How can I adapt this example to work in clojurescript? http://clojuredocs.org/clojure.core/with-out-str#example-590664dde4b01f4add58fe9f

I'm combing the clojurescript codebase to try and find with-out-str, but no such luck yet

nvm, I found it: https://github.com/clojure/clojurescript/blob/9dc684695cee889001d36fbe0753c8aae8dc209b/src/main/clojure/cljs/core.cljc#L2770

why is it that set does not support indexOf?

sets are unordered and not sequential so how would they?

ohh, so a sorted set does?

index-of is a mapping of value to key, i.e. vectors. sets have no values, they only have keys

map: explicit key, explicit value vector: implicit key (monotonic integer 0 based), explicit value set: explicit key contains? works with keys in all three instances.

sorted-* describes the order of the keys when enumerating them

@hkjels @robert-stuttaford Fortunately we have docs on this now. sequential? is part of the answer. See https://clojurescript.org/reference/javascript-api

hi all, what’s the state of the art Clojurescript at the moment? There are quite some options reagent, Om, re-frame. Question for someone who’s tried these out: what would you chose for the next project and what not?

re-frame is state management that builds on top of reagent, they are not comparable

and I would choose that (reagent with re-frame on top) without a doubt

@dennisa I would go with om for large, complex apps. Otherwise, I quite like rum.

@danielstockton Thanks, why do you like rum and for what purposes?

I like rum for it's simplicity, when you don't have complicated state management requirements. It's lightweight. Om is state of the art in terms of untangling complex state management requirements.

@dennisa Check out this beauty: https://github.com/Day8/re-frame-10x

Om let's you completely decouple the state from your components. I believe re-frame does too, to some extent, but I don't think it provides the same power to reason about the state requirements of an app as a whole. Someone please correct me if I'm wrong.

Om is most powerful when paired with a backend query parser.

If you're trying to integrate with separate REST endpoints, then it might not be the best fit, but I would no longer say that's state of the art.

You could write a parser that sits in front of separate REST endpoints though...

I’m working right now in Fulcro application, and, at least for me, it made right choices: afaict in Om you bring your own parser, so your application is not 100% predictable, compared to Fulcro. Even in React: people are starting adopt Apollo: they added in-memory graphql-store, to use graphql for local state, so Redux/Mobx are not necessary.

In Redux there’s a pattern called ICC https://slides.com/mr-mig/microsoft-to-do-23#/ in which you’re having normalized state just like in Fulcro. But comes close to it, but state structure is not demand driven.

is there a fressian implementation for ClojureScript?

https://github.com/kawasima/fressian-cljs

beware that it is unmaintained

I made a PR in march 2017 for encoding ArrayBuffers and it's still there untouched