@paulspencerwilliams they have a JVM languages track but I haven't checked if they've published all the speakers yet so not sure. They had a bit on Scala, Frege and @jr0cket did a workshop on Clojure last year

@yogidevbear It's not necessary, but kind of inevitable. You'll end up using React (somewhat reactive), most likely through reagent (more reactive) and maybe even re-frame on the top (to provide patterns... reactive)...

@not-raspberry Maybe I'm just missing something, but React (the FB stuff) felt more like a shiny new toy than a solid solution. My understanding (which could be flawed) is that it's purely for creating UI components/elements and is particular disconnected from any real business/interaction logic as such (e.g. only the V in any MV* systems/frameworks). I'm not sure how closely this matches up to that other website's tag line of "An API for asynchronous programming with observable streams". Isn't reagent/re-frame only one of the ways to "skin the cat"? I also thought that ClojureScript could be compiled into native JS to still benefit from the FP awesomeness of Clojure? This doesn't equate to React. Post script: I'm not trying to disagree with anyone here, just trying to understand this a bit better :slightly_smiling_face:

@yogidevbear I think of React.js and it's cljs wrappers (reagent, re-frame, Om and Om.next) as providing MVC on the client where the M is sometimes delegated to the server in the form of http or web socket calls for data.

@yogidevbear yes React.fb is different from the http://reactivex.io projects and is view-focused. it plays very well with things like re-frame though - and re-frame is very much more of the "API for asynchronous programming with observable streams" mould