Hello everyone. A small comment, about Scala API: main commiters are hardly available, as for today.
As for Clojure - I might suggest that it might be possible to enlight future work, for that package, for Clojure developers. On Mon, Jun 4, 2018 at 8:50 PM, Naveen Swamy <mnnav...@gmail.com> wrote: > Hi Carin, > > This is great effort and very nicely documented. When I surveyed at my day > job on the interest for Scala packages there were a few people who > specifically were interested in the Clojure packages, I think those are > people who might have tried and understand the complexity of making Scala > work in Clojure. > > I am in support of a MXNet-Clojure package, I request you to add more unit > tests and integration tests that can be ported to CI. > > Thanks for your efforts. > > -Naveen > > > > On Fri, Jun 1, 2018 at 6:16 PM, Carin Meier <carinme...@gmail.com> wrote: > > > It is always a good thing to consider the cost with the benefit. I'll do > my > > best to explain what I see the tradeoffs to be. > > > > First, I wanted to clarify that it took significant development effort to > > get the Clojure package and the interop working properly despite my > simple > > looking design on the confluence page :) > > > > One of the advantages of MXNet over its competitors is its many language > > support. The Clojure package would only increase the value of this > > proposition and bring new users and growth into the community. > > However, there is a cost associated with adding this language support as > > you pointed out. > > > > Since the Clojure package right now is only reliant on the Scala jars > from > > Maven, it can exist outside the main project as an independent repo but I > > think that would lessen the growth benefit both to the Clojure community > > and to the MXNet community to not be included as a first class language. > > > > I believe having first class Clojure support in MXNet is valuable, but > the > > cost of that support is up to the community to decide. > > > > Is there a process for considering a new package in MXNet? > > > > - Carin > > > > On Fri, Jun 1, 2018 at 5:51 PM, Chen HY <chenhy12...@gmail.com> wrote: > > > > > Have checked the issue and the confluence page, but still curious. > > > Clojure and Scala are both JVM based languages. > > > They, as well as many JVM based languages, can share their class and > > method > > > at a certain level. > > > Why should the community maintain two APIs for two languages with can > > share > > > their packages with almost zero effort? > > > > > > > > > 2018-06-01 21:58 GMT+01:00 Carin Meier <carinme...@gmail.com>: > > > > > > > Hi all, > > > > > > > > I've been working on a Clojure package for MXNet. Since Clojure is a > > JVM > > > > language, the package leverages the great work of the existing Scala > > > > package. > > > > > > > > I would appreciate any feedback and testing. > > > > > > > > Here is the original issue: > > > > https://github.com/apache/incubator-mxnet/issues/8971 > > > > > > > > Architecture & Design: > > > > https://cwiki.apache.org/confluence/display/MXNET/MXNet+Clojure > > > > > > > > and the github repo for rapid testing and issue fixing before of > > opening > > > an > > > > official PR https://github.com/gigasquid/clojure-mxnet > > > > > > > > I'm also active in the slack channel so feel free to ping me there. > > > > > > > > Thanks, > > > > Carin Meier > > > > > > > > > > > > > > > > -- > > > Chen Hanyang 陈涵洋 > > > Software School Fudan University > > > +86-138-1881-7745 > > > > > >
