I vote for "upgrade/rewrite Scala API and bring up MXNet 2.0 features" as it took us a lot of efforts to bring MXNet to Scala originally and there are already adopters of Scala API in industries.
On Fri, Mar 6, 2020 at 11:02 AM Wang Jiajun <notificati...@github.com> wrote: > > We may also drop ONNX in MXNet 2. I'm not aware of anyone working on > ONNX in MXNet and TVM can be used as a replacement. > > +1 for keeping ONNX support. Although it has a lot of small problems, but > I've converted a lot of pytorch models to mxnet for deploying with the > following pipeline: > > https://docs.aws.amazon.com/dlami/latest/devguide/tutorial-onnx-pytorch-mxnet.html > > -- > 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-595835658 -- Yuan Tang https://terrytangyuan.github.io/about/ <http://twitter.com/TerryTangYuan> <https://terrytangyuan.github.io/about/>
