Re: Officially support Vert.x

2018-01-16 Thread lawrence . krubner
James Gatannah, I apologize for hijacking this thread, but what did you mean here: > The one useful thing I could find that Vert.x provides out of the box > that clojure doesn't is the pub/sub messaging. That turned our > architecture into spaghetti, so I wouldn't call it a win. Was there

Re: Officially support Vert.x

2018-01-10 Thread Matching Socks
How do the aims of this undertaking compare with Pedestal? http://pedestal.io/ says, "Pedestal supports Tomcat, Jetty, Immutant (with Undertow), Vert.x, ..." -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to

Re: Officially support Vert.x

2018-01-10 Thread Timothy Baldridge
A few other points of design: 1) Move the requires into the `ns` form: (ns example.simple-http-server (:require [io.vertx.clojure.core.core :as core] [io.vertex.lang.clojure.vertx :as vertx])) 2) If you make sure that your functions always return the first argument passed to

Re: Officially support Vert.x

2018-01-10 Thread Feuer Au
Thanks a lot we modify the hello code to following: (ns examples.simple-http-server) (require '[io.vertx.clojure.core.core :as core] '[io.vertx.lang.clojure.vertx :as vertx] '[io.vertx.lang.clojure.http-server :as server] '[io.vertx.lang.clojure.http-server-request :as request]

Re: Officially support Vert.x

2018-01-10 Thread Gary Verhaegen
It’s not clear what the "do" is supposed to mean in those defns (unless there’s some deep dark magic going on, they are currently not doing anything and you can just remove them), and you very likely want "let" instead of "def" for the local variables. def in Clojure does not follow lexical

Re: Officially support Vert.x

2018-01-10 Thread Feuer Au
And here is the simple example "Hello from Vert.x!" like other languages on the Vert.x official frontpage: (ns examples.simple-http-server) (require '[io.vertx.clojure.core.core :as core] '[io.vertx.lang.clojure.vertx :as vertx] '[io.vertx.lang.clojure.http-server :as server]

Re: Officially support Vert.x

2018-01-10 Thread Feuer Au
Hi Toby: We just complete most parts of vertx-lang-clojure, here is the project address: https://github.com/chengenzhao/vertx-lang-clojure all reviews and suggestions and issues and PRs are welcomed Cheers On Friday, December 29, 2017 at 8:50:53 PM UTC+8, Toby Crawley wrote: > > The short

Re: Officially support Vert.x

2018-01-09 Thread Feuer Au
Hi Toby: We start working on Vert.x Clojure implementation https://github.com/chengenzhao/vertx-lang-clojure and for now we have made some progresses now we could generate "Hello from Vert.x!" example and deploy ClojureVerticle and the clojure code wrapper is almost there (ns

Re: Officially support Vert.x

2017-12-31 Thread James Gatannah
Disclaimer: I once spent 3-4 weeks studying Vert.x's design philosophy and architecture. So I'm hardly an expert. On Saturday, December 30, 2017 at 9:31:47 AM UTC-6, Feuer Au wrote: > > Hmm > yes it is almost an absolute requirement since we have already invested a > lot in Java, Kotlin,

Re: Officially support Vert.x

2017-12-30 Thread Timothy Baldridge
Multi-process polyglot systems I understand, they aren't common, but I've seen them. In most cases, immutable queues and HTTP APIs work great. But (and pardon my bluntness), why would I ever want a polyglot single process system? That sounds like a major design mis-step. The overhead of mental

Re: Officially support Vert.x

2017-12-30 Thread Feuer Au
Hmm yes it is almost an absolute requirement since we have already invested a lot in Java, Kotlin, Javascript and other languages based on Vert.x and for Clojure & Haskell are pretty new candidates for us, we need to find a way to persuade our programmers to use these languages and Vert.x is

Re: Officially support Vert.x

2017-12-30 Thread Feuer Au
Thanks Toby for the answer We are thinking of using purely functional programming languages with Vert.x since we have already tasted some benefits from functional programmings e.g. using Kotlin/Scala top level functions etc. and it might not be only Clojure we try to import but also

Re: Officially support Vert.x

2017-12-29 Thread Alan Moore
As Gary said there are options if you aren’t tied to Vert.x. Of course there is core.async but you might also take a look at Manifold: http://aleph.io/manifold/rationale.html Good luck! Alan -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post

Re: Officially support Vert.x

2017-12-29 Thread Gary Verhaegen
Is vert.x an absolute (external) requirement, or is that a tool you want to use to achieve some goal? If the latter, maybe there are other tools in the Clojure ecosystem that you could use instead? On 29 December 2017 at 13:49, Toby Crawley wrote: > The short answer is no,

Re: Officially support Vert.x

2017-12-29 Thread Toby Crawley
The short answer is no, there is no Clojure support for Vert.x 3 that I know of. The longer answer: I wrote the Clojure language module for Vert.x 2, which had a pretty low usage rate, partially because core.async was released around the same time. When Vert.x 3 was being written, the Vert.x team

Officially support Vert.x

2017-12-28 Thread Feuer Au
Hi All, Curious about Vert.x is officially supported? We tried to use some new languages on JVM e.g. Scala, Kotlin etc. and be interested in using some relatively purely functional programming languages and so far Clojure is our best bet but unfortunately couldn't find native Clojure api on