Emilio

@pmonks nevermind, I managed to solve it.

@pmonks I couldn't get it working with node, although I think there's a fork of Hickory that does support it. What I did was to use PhantomJS, and also the...

@pmonks Definitely. I'll update the readme when I'm done as this is probably not the only caveat, unfortunately. The single-origin policy will limit its use mostly to react-native, I'm afraid....

@pmonks very helpful reference indeed. I still haven't been able to successfully deal with the fact that the HTTP clients in ClojureScript are asynchronous, while in Clojure they're not. Do...

@pmonks Indeed I was able to handle the request inside the `go` block. The problem is, I don't know how to *return* that value. Every time I try to return...

@pmonks Today I finally understood something I kinda suspected already. JavaScript [never blocks](https://developer.mozilla.org/en-US/docs/Web/JavaScript/EventLoop#Never_blocking) because it is single-threaded. This is true for the browser and [for Node.js](https://nodejs.org/en/docs/guides/blocking-vs-non-blocking/#concurrency-and-throughput). That's why Clojure's core.async...

I agree that, for the sake of compatibility, it makes sense to provide an asynchronous version on the Clojure side as well. However, I also believe that the synchronous version...

@pmonks I just finished. I didn't touch the documentation yet. Finally, instead of a callback, I kept the channel. That's the most clojuresque way. As you will see, my changes...

I will work on this on Wednesday, no need to worry!

I'll be working on it today. No worries.