lanking520 commented on issue #17783:
URL: 
https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-665771813


   @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.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to