Hi all, after talking with @frankfliu, I think we can donate DJL's MXNet JNA (source code) to Apache MXNet for the low level Java support. Having that, Apache MXNet will be able to build from source generating all frontend low level Java API for users to use. The good part is it's maintainance cost, it require very minimal dependencies and everything is generated:
https://github.com/awslabs/djl/tree/master/mxnet/jnarator User will be able to leverage on that directly. >From the usability point of view, JavaCPP will also offer similar >funcionalities. @saudet will you be open to consider if MXNet JavaCPP can be >fully donated to Apache MXNet and maintained by community? These two solution is very similar and potentially JavaCPP can bring some level of performance improvement. My only concern to JavaCPP is @szha initial question, how we are going to build/maintain the Java package. Having a Java API is essential to the community since it can be used by many more JVM based languages. @hmf I would +1 on the usability you have mentioned for Scala. However, from the historical reason when we would like to build Java compatible API from MXNet Scala, there are huge obstacles blocking us moving forward. Some Scala representation require addtional effort to be used in Java. However if using Java in Scala, it is 100% supported. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/apache/incubator-mxnet/issues/17783#issuecomment-700374199
