Hi there, I am too a little concerned about dropping module support. Since a large percent of the user based started with module APIs, dropping that support could alienate the user base.
I got familiar around mxnet-1.3. The main functions I appreciate are: 1. sparse vector symbols - which are still best supported on module API or Symbol-Gluon; 2. control flow operators - which allow people to create basically any arbitrary operator that they would want (though it is still not quite arbitrary); 3. linalg package - some quite sophisticated algorithms that would not be easy to replicate. 4. Hybridize - some amount of input validation is desirable in shared libraries. I am not looking for the speed change, but rather the idea that I can easily catch the edge cases with a defined graph. To the gist of it, I do want to see more supports such as memory estimation / compute time estimation / nan checking, some of which are available in TVM. -- 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-639087830
