mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tianqi Chen <tqc...@cs.washington.edu>
Subject Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.
Date Sat, 23 Mar 2019 00:09:04 GMT
I think GluonCV and GluonNLP are useful domain specific libraries that
build on top of MXNet. And it is perfectly fine to go with the current
established names.

Tianqi

On Fri, Mar 22, 2019 at 4:57 PM Mu Li <muli.cmu@gmail.com> wrote:

> Are you proposing to rename Gluon? I think Pedro's opinion is about a
> better way to communicate what's Gluon and how it's related to MXNet.
>
> On Fri, Mar 22, 2019 at 4:54 PM Davydenko, Denis <dden@amazon.com.invalid>
> wrote:
>
> > I support idea of putting brands of MXNet and Gluon closer together. I
> > agree with your argument, Mu, but MXNet is quite far away from TF place
> at
> > this time so I don’t know how well that argument is transferable from TF
> > position to MXNet position.
> >
> > MXNet Imperative is definitely too restrictive of a name, we can come up
> > with better one... MXNet-M for example, stands for MXNet-Modified
> (military
> > connotation). If naming is the only thing we need to figure out - that
> is a
> > good place to be in __
> >
> > --
> > Thanks,
> > Denis
> >
> > On 3/22/19, 4:48 PM, "Mu Li" <muli.cmu@gmail.com> 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 <terrytangyuan@gmail.com>
> > wrote:
> >
> >     > +1
> >     >
> >     > On Fri, Mar 22, 2019 at 7:29 PM Lin Yuan <apeforest@gmail.com>
> > 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 <
> >     > pedro.larroy.lists@gmail.com
> >     > > >
> >     > > 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.
> >     > > >
> >     > >
> >     >
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message