mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lin Yuan <>
Subject Re: [DISCUSS] Rebrand Gluon to MXNet imperative or something MXNet.
Date Fri, 22 Mar 2019 23:29:21 GMT

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?


On Fri, Mar 22, 2019 at 4:02 PM Pedro Larroy <>

> 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.

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