Re: core.async top use cases

2016-09-18 Thread Rangel Spasov
http://aleph.io/aleph/literate.html "Alternately, we can use a core.async goroutine to create our response, and convert the channel it returns using manifold.deferred/->source, and then take the first message from it. This is entirely equivalent to the

Re: Clojure support for Visual Studio Code

2016-09-18 Thread Andrey Lisin
I've just published the new release that addresses the issues Michael pointed out. I've also added the new 'Eval and show the result' command which evaluates a file and prints the result into a VSCode output channel. Feel free to try it out. You can download the new release here:

Re: Abridged summary of clojure@googlegroups.com - 10 updates in 6 topics

2016-09-18 Thread many
documenat se z@3 QAzUqa, a qd https://docs.google.com/documenat/qd/1e5sFTSpVIt-x9WCWF6auM3O4dWv0i0asdgUgSl9H9Qa6S8/edit?uspdrivesSdktzjt EUÍdrivesdkqda olp and _ On Tue, Sep 6, 2016, 7:31 PM wrote: > clojure@googlegroups.com >

Re: Clojure support for Visual Studio Code

2016-09-18 Thread Andrey Lisin
Hi Michael, First of all, I would like to thank you for your feedback, it helps a lot. See my comments inlined. On Saturday, September 17, 2016 at 4:32:39 AM UTC+6, Michael Ball wrote: > > > - Explicit docs/instructions on how to start and connect to the repl would > be good. I was able to get

core.async top use cases

2016-09-18 Thread Matan Safriel
Hi, It's very easy to see how core.async solves callback hell for front-end development with clojurescript. In what use cases would you use it for server-side? we already have non-blocking IO from Java, and we have clojure agents. So what's a bunch of salient use cases? Are there prominent

Re: Clojure support for Visual Studio Code

2016-09-18 Thread Andrey Lisin
Hi Ikuru, please, see my comments below. On Sunday, September 18, 2016 at 6:52:47 AM UTC+6, Ikuru Kanuma wrote: > > > I guess the installation part is then something specific to the ubuntu > flavor(I am using ubuntu-mate) I am using/ what ever it could be. > (I also did try to open the file