-1 for now. Respectfully I have some concerns. First, Gluon is about a new programming paradigm, neither symbolic programming nor imperative, but both. It brings concrete benefit for both prototyping and deployment. To help customers best enjoy the benefit of Gluon, we need more advertisement, more clarification, rather than trying to prevent customers from knowing the fact such great thing exists.
Second, every time you rebrand, you confuse customers. To rebrand is not to attract, but to continue confuse more customers. Suppose the name Gluon disappears, how do you guys differentiate it between the less flexible MXNet symbolic, and between the less deployment-friendly MXNet imperative? Last but not least, the name Gluon, which has been well respected and cited by many peers who do DL framework research, as the simple and effective way to unify the two paradigms. There is no reason to destroy our brand. I really would love to mention, if we really want a framework to be great, we need more advertisement of how Gluon addresses customers pain point, rather than making it disappear. On Fri, Mar 22, 2019 at 4:48 PM Mu Li <[email protected]> wrote: > Gluon is about imperative neural network training and data loading. ndarray > is another large imperative module. Besides, Gluon also supports symbolic > execution after hybridizing. mxnet imperative might not be a good name for > it. Another choice is high-level API, that's how TF talks about Keras. > > On Fri, Mar 22, 2019 at 4:38 PM Yuan Tang <[email protected]> wrote: > > > +1 > > > > On Fri, Mar 22, 2019 at 7:29 PM Lin Yuan <[email protected]> wrote: > > > > > +1. > > > > > > Just to give some of my real experience: > > > 1) I advertised a recent GluonNLP blog and many responses are "This > seems > > > nice. So is Gluon a new library to replace MXNet?" > > > 2) We visited customers in a unicorn company who showed interests in > > MXNet > > > but none of the engineers knew the relationship between > GluonNLP/GluonCV > > > and MXNet > > > 3) When integrating MXNet to Horovod and adding examples, I received > > > comments like "What is Gluon? Is it a new library in addition to > MXNet?" > > > > > > Everyone is talking about PyTorch nowadays, but not Caffe2 anymore > > although > > > the latter is still serving as a backend component. Maybe we should > also > > > doubledown on one brand? > > > > > > Lin > > > > > > On Fri, Mar 22, 2019 at 4:02 PM Pedro Larroy < > > [email protected] > > > > > > > wrote: > > > > > > > Hi dev@ > > > > > > > > We heard feedback from users that the Gluon name is confusing. Some > of > > > > them don't even know it's MXNet and it's unclear the relationship > with > > > > MXNet > > > > > > > > Would it make sense to rebrand Gluon to just MXNet or MXNet > > > > imperative? Diluting brands and names is never a good idea. > > > > > > > > There's also gluonhq which is related to JavaFX which adds to the > > > > confusion, search engine friendliness is not high as well. > > > > > > > > Pedro. > > > > > > > > > >
