Let's continue the discussion on website in #17497
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17701#issuecomment-595544177
Closed #17701.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17701#event-3103498526
@gigasquid Yeah, you can view the download statistics from
https://repository.apache.org/#central-stat.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/apache/incubator-mxnet/issues/17676#issuecomment-595522607
Is there anyway to get the stats on downloads of the maven central
scala/clojure jars to see how much current use there is? If the numbers are
high or low and what trend is can help shape the decision
--
You are receiving this because you authored the thread.
Reply to this email directly or
@gigasquid @zachgk Since the Scala API are built a while ago, I can see some of
the deprecated sections: Module, DataparallelGroup, Symbol ... Most of the
training component would be invalid. There can be three approaches:
- upgrade/rewrite Scala API and bring up MXNet 2.0 features.
- drop Scala
Further thinking this through - since the Scala language binding currently
provides the base for both Java and Clojure, I would be nice to know what the
future plans for the Scala language binding is. Whether or not that path is
supported will determine the other JVM langs.
--
You are
If I understand this correctly, since the Scala, Java, and Clojure bindings use
symbol and ndarray exclusively, this will also mean that they will be
effectively deprecated as well.
This is fine if what the community decides upon, but it should be called out
explicitly.
cc @lanking520 @nswamy
