2015-04-14 10:51 GMT+02:00 Hildeberto Mendonça <[email protected]>:

> On Tue, Apr 14, 2015 at 9:43 AM, Romain Manni-Bucau <[email protected]
> >
> wrote:
>
> > hmm,
> >
> > so it seems the readme is not yet complete ;)
> >
>
> Documentation is a continuous effort. Now we have a release, we will
> finally give more attention to it. Did you miss something there? Any
> difficulty that we can simplify?
>
>
well surely the roadmap part and the template side is a bit "light" today
(typically I need far more properties for prod - not for other environments.


>
> > btw tomee has a ssh connector with some commands (
> >
> https://rmannibucau.wordpress.com/2012/05/09/tomee-and-its-ssh-connector/
> > ).
> >
>
> That's good material. Thanks for sharing. Btw, your first sentence there
> "TomEE is a simple but great container." represents exactly the philosophy
> behind Clojure. Good that we are not bringing something complex to the
> table. It means, as a community, we may not "speak" the same language but
> we think exactly the same way. ;-)
>
>
Sure, my point was more about "merging" communities. Just checking github
projects you often see "i rewrote it cause it was not in my language".


>
> > That said joining our efforts would still be good and even if in 3 lines
> of
> > clojure you avoid maybe 10 lines of java you stay "alone" in term of
> > community and you can't assume you have clojure on prod machines IMO and
> > that "prod" guys can write clojure - but you can assume you have java and
> > that prod guys are shell expert, no?
> >
>
> We are literally joining your effort, but in a different repository and in
> another language. This is not a contribution to TomEE's code base, but it's
> definitely a contribution to TomEE's ecosystem. We are aware of the risk of
> having less contributors, but what actually motivates us is to deliver a
> new functionality in the shortest amount of time we can possibly get,
> preserving the same level of performance and robustness of the JVM.
>
>
Let's try and see what is happening, maybe I'm not optimist enough - but
well I'm french ;)


> Btw, Clojure is just one more jar in the app ;-) When people install
> TomEE-CLI, all dependencies are downloaded automatically. They don't even
> realise that Clojure is there. When they pass the commands to the command
> line they don't even realize they are actually programming in clojure. For
> instance, install TomEE:
>
>
That's more about default environment otherwise you are right.


> // Install the latest version of TomEE web profile in the working
> directory.
> (install-tomee)
>
> // Install the latest version of TomEE Plus in the working directory.
> (install-tomee :dist "plus")
>
> // Install the version 1.7 of TomEE Plus in the path /opt.
> (install-tomee :version "1.7" :dist "plus" :location "/opt")
>
> These are valid Clojure expressions, as simple as command lines. We are
> simply calling our functions there.
>
>
Ask a shell guys, it is weird and when he'll get a syntax error it will not
be obvious - once again just real feedback, tried groovy in prod as
"interface" and was already too much.


> I know, the actual Clojure source code looks strange. That's what I thought
> when I first looked at it. But I can tell you that I'm not that smart, but
> I was able to grasp the language in less than a month. I started learning
> Clojure in January only during my free time, sharing this time with two
> little kids under 3.5 years old, and now I'm releasing software with it.
> When I became parent I realized time is my most important resource. I
> simply can't waste it anymore.
>
> So, we will be happy when we finally have contributors, but we will be even
> happier when we have many happy users \o/
>

So you have to do .deb and .rpm ;). That's surely your best way to promote
it without loosing guys on the road.

Reply via email to