mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lanking <>
Subject Re: [apache/incubator-mxnet] [RFC] MXNet 2.0 JVM Language development (#17783)
Date Wed, 29 Jul 2020 16:37:05 GMT
@saudet Thanks for your reply. Still, I am concerned about the first question:

you mentioned:
> We can go either way, but I found that for contemporary projects like Deeplearning4j,
MXNet, PyTorch, or TensorFlow that > need to develop high-level APIs on top of something
like JavaCPP prefer to have control over everything in their own
> repositories, and use JavaCPP pretty much like we would use cython or pybind11 with setuptools
for Python.

We are looking for a robust solution for MXNet Java developers to use especially owned and
maintained by the Apache MXNet's community. I will be more than happy to see if you would
like to contribute the source code that generate MXNet JavaCpp package to this repo. So we
can own the maintainance and responsible for the end users that the package is reliable.

At the beginning, we were discussing several ways that we can try to preserve a low level
Java API for MXNet that anyone who use Java can start with. Most of the problems were lying
under the ownership and maintainance part. I have placed JavaCpp option to option 5 so we
can see which one works the best in the end.

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message