You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Chris Olivier <cj...@gmail.com> on 2018/04/11 17:18:12 UTC
MXNet Name Change?
Should we consider renaming MXNet to something more "friendly"?
IMHO, I think this may be related to adoption problems.
MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
Tensorflow, PyTorch, Caffe -- sound cool.
Re: MXNet Name Change?
Posted by "Barber, Christopher" <Ch...@analog.com>.
Yes, I think it is kind of late to try to get people to say "mix-net" and it makes it seem like yet another complex technology that no one even knows how to pronounce (e.g. LaTeX). Most English speakers are going to say "em-ex-net". If you really want people to say "mix-net" then you should spell it that way, IMO.
On 4/11/18, 4:59 PM, "Rahul Huilgol" <ra...@gmail.com> wrote:
Even changing the pronunciation is not an easy thing to do IMHO. As someone
who has been working on MXNet for the last 8 months, this thread is the
first time I am reading that MXNet is supposed to be pronounced 'mix-net'.
We risk losing the momentum even if we try to steer the pronunciation
towards something which is not popular currently.
I agree Gluon is a friendlier/cooler name. But since we are trying to
present Gluon as an interface which multiple frameworks can implement, I'm
not sure if we should try to shift the focus away from MXNet and towards
Gluon.
As far as adoption goes, I agree with Christopher that public benchmarks or
blog posts about how MXNet is better or more usable than other frameworks
would be worth spending effort on. Rebranding in a way to not lose the
existing momentum honestly sounds more difficult than this :)
By the way, we had some talk of a new friendlier logo sometime back. What
happened to that?
On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <aa...@gmail.com>
wrote:
> Changing branding is hard as we already have some momentum under the
> current name. It's not impossible, and if someone has a fantastic idea
> and marketing plan for it, it's worth considering.
>
> Aside from that, updating the pronunciation could be useful if you
> like having those gif vs jif debates, but at least people would be
> talking about it. I personally like the sound of "mix-net" over
> "em-ex-net". Since we're just starting Youtube videos, I think it's a
> great idea to establish the pronunciation right away in those videos.
>
>
>
> On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com>
> wrote:
> > Just curious why you think it’s a bad idea — you didn’t say?
> >
> > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com> wrote:
> >
> >> At least people needs a way to speak it.
> >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> agreed
> >> one everywhere helps a lot.
> >> Changing name is a bad idea.
> >>
> >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> >>
> >> > Agree that MXNet, the combination of Minerva and CXXNet, which can be
> >> > interpreted as mixed-net, is hard to be pronounced. But rebranding a
> name
> >> > is a very big decision. We need a very carefully designed marketing
> plan
> >> > for it.
> >> >
> >> > A choice is that we can gradually refer MXNet as a backend, and talk
> more
> >> > about the frontend Gluon.
> >> >
> >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> >> > thomas.delteil1@gmail.com>
> >> > wrote:
> >> >
> >> > > FWIW Brainscript is actually a network definition language:
> >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> >> > > BrainScript-Network-Builder
> >> > >
> >> > >
> >> > >
> >> > > Thomas
> >> > >
> >> > >
> >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> >> > >
> >> > > > IIRC CNTK renamed to something like brainscript which does not
> seem
> >> to
> >> > be
> >> > > > very successful publicity campaign?
> >> > > >
> >> > > > Chiyuan
> >> > > >
> >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> >> cjolivier01@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Should we consider renaming MXNet to something more "friendly"?
> >> > > > >
> >> > > > > IMHO, I think this may be related to adoption problems.
> >> > > > >
> >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't
> >> they?
> >> > > > >
> >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> >> > > > >
> >> > > > --
> >> > > > Semt ftom m ipohne
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Chen Hanyang 陈涵洋
> >> Software School Fudan University
> >> +86-138-1881-7745
> >>
>
--
Rahul Huilgol
Re: MXNet Name Change?
Posted by Chris Olivier <cj...@gmail.com>.
Well, I suppose for a sufficiently cool name, you could go like
CoolName-MXNet for awhile and then transition just into CoolName. Like how
Johnny Cougar transitioned into John Melloncamp back in the 80’s by
transitioning through “John Cougar Melloncamp” and then eventually dropping
the “Cougar”. Just sayin’.
On Wed, Apr 11, 2018 at 1:59 PM Rahul Huilgol <ra...@gmail.com>
wrote:
> Even changing the pronunciation is not an easy thing to do IMHO. As someone
> who has been working on MXNet for the last 8 months, this thread is the
> first time I am reading that MXNet is supposed to be pronounced 'mix-net'.
> We risk losing the momentum even if we try to steer the pronunciation
> towards something which is not popular currently.
>
> I agree Gluon is a friendlier/cooler name. But since we are trying to
> present Gluon as an interface which multiple frameworks can implement, I'm
> not sure if we should try to shift the focus away from MXNet and towards
> Gluon.
>
> As far as adoption goes, I agree with Christopher that public benchmarks or
> blog posts about how MXNet is better or more usable than other frameworks
> would be worth spending effort on. Rebranding in a way to not lose the
> existing momentum honestly sounds more difficult than this :)
>
> By the way, we had some talk of a new friendlier logo sometime back. What
> happened to that?
>
> On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <aa...@gmail.com>
> wrote:
>
> > Changing branding is hard as we already have some momentum under the
> > current name. It's not impossible, and if someone has a fantastic idea
> > and marketing plan for it, it's worth considering.
> >
> > Aside from that, updating the pronunciation could be useful if you
> > like having those gif vs jif debates, but at least people would be
> > talking about it. I personally like the sound of "mix-net" over
> > "em-ex-net". Since we're just starting Youtube videos, I think it's a
> > great idea to establish the pronunciation right away in those videos.
> >
> >
> >
> > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com>
> > wrote:
> > > Just curious why you think it’s a bad idea — you didn’t say?
> > >
> > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com>
> wrote:
> > >
> > >> At least people needs a way to speak it.
> > >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> > agreed
> > >> one everywhere helps a lot.
> > >> Changing name is a bad idea.
> > >>
> > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> > >>
> > >> > Agree that MXNet, the combination of Minerva and CXXNet, which can
> be
> > >> > interpreted as mixed-net, is hard to be pronounced. But rebranding a
> > name
> > >> > is a very big decision. We need a very carefully designed marketing
> > plan
> > >> > for it.
> > >> >
> > >> > A choice is that we can gradually refer MXNet as a backend, and talk
> > more
> > >> > about the frontend Gluon.
> > >> >
> > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > >> > thomas.delteil1@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > FWIW Brainscript is actually a network definition language:
> > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > >> > > BrainScript-Network-Builder
> > >> > >
> > >> > >
> > >> > >
> > >> > > Thomas
> > >> > >
> > >> > >
> > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> > >> > >
> > >> > > > IIRC CNTK renamed to something like brainscript which does not
> > seem
> > >> to
> > >> > be
> > >> > > > very successful publicity campaign?
> > >> > > >
> > >> > > > Chiyuan
> > >> > > >
> > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > >> cjolivier01@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Should we consider renaming MXNet to something more
> "friendly"?
> > >> > > > >
> > >> > > > > IMHO, I think this may be related to adoption problems.
> > >> > > > >
> > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use,
> don't
> > >> they?
> > >> > > > >
> > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > >> > > > >
> > >> > > > --
> > >> > > > Semt ftom m ipohne
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Chen Hanyang 陈涵洋
> > >> Software School Fudan University
> > >> +86-138-1881-7745
> > >>
> >
>
>
>
> --
> Rahul Huilgol
>
Re: MXNet Name Change?
Posted by xinfan meng <mx...@gmail.com>.
How about a Capricorn: mixed, cool and easily recognized.
On Thu, 12 Apr 2018 at 11:24, xinfan meng <mx...@gmail.com> wrote:
> Not sure about changing name. But for branding, how about designing a
> mascot? No other frameworks have one yet.
> On Wed, 11 Apr 2018 at 23:01, Anirudh <an...@gmail.com> wrote:
>
>> Release naming sounds like a great idea. But we would need this for the
>> minor releases too, since many of our customers seem to be switching
>> between different minor releases.
>>
>> On Wed, Apr 11, 2018 at 2:39 PM, Chris Olivier <cj...@gmail.com>
>> wrote:
>>
>> > Ha! good one, Ly!
>> > Let's not forget, though, a high percentage of us know who Sean Combs
>> is. I
>> > couldn't tell you one of his songs, his name changes were a
>> differentiator.
>> >
>> > Makes me think of something -- still another possibility could be the
>> > naming of major releases. Like Android does, for instance. "MXNet
>> Alien",
>> > for instance for 2.0 (alien just being an example since my home PC is an
>> > Alienware). No one else is doing that and it doesnt make me think of
>> > something uncomfortable like "M-X-Net" does by itself.
>> >
>> >
>> > On Wed, Apr 11, 2018 at 2:21 PM Ly Nguyen <ng...@gmail.com> wrote:
>> >
>> > > I agree with comments on not breaking momentum by rebranding the name.
>> > It's
>> > > also my first time hearing about the pronunciation being "mixnet" and
>> not
>> > > "m-x-net" so that clarification, along with the motivation behind the
>> > name,
>> > > feature parity, would strengthen the brand more.
>> > >
>> > > To that point, Sean Comb's evolution of 5 different names was more
>> > > confusing than it was helpful. :)
>> > >
>> > > On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol <
>> rahulhuilgol@gmail.com>
>> > > wrote:
>> > >
>> > > > Even changing the pronunciation is not an easy thing to do IMHO. As
>> > > someone
>> > > > who has been working on MXNet for the last 8 months, this thread is
>> the
>> > > > first time I am reading that MXNet is supposed to be pronounced
>> > > 'mix-net'.
>> > > > We risk losing the momentum even if we try to steer the
>> pronunciation
>> > > > towards something which is not popular currently.
>> > > >
>> > > > I agree Gluon is a friendlier/cooler name. But since we are trying
>> to
>> > > > present Gluon as an interface which multiple frameworks can
>> implement,
>> > > I'm
>> > > > not sure if we should try to shift the focus away from MXNet and
>> > towards
>> > > > Gluon.
>> > > >
>> > > > As far as adoption goes, I agree with Christopher that public
>> > benchmarks
>> > > or
>> > > > blog posts about how MXNet is better or more usable than other
>> > frameworks
>> > > > would be worth spending effort on. Rebranding in a way to not lose
>> the
>> > > > existing momentum honestly sounds more difficult than this :)
>> > > >
>> > > > By the way, we had some talk of a new friendlier logo sometime back.
>> > What
>> > > > happened to that?
>> > > >
>> > > > On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <
>> > > aaron.s.markham@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Changing branding is hard as we already have some momentum under
>> the
>> > > > > current name. It's not impossible, and if someone has a fantastic
>> > idea
>> > > > > and marketing plan for it, it's worth considering.
>> > > > >
>> > > > > Aside from that, updating the pronunciation could be useful if you
>> > > > > like having those gif vs jif debates, but at least people would be
>> > > > > talking about it. I personally like the sound of "mix-net" over
>> > > > > "em-ex-net". Since we're just starting Youtube videos, I think
>> it's a
>> > > > > great idea to establish the pronunciation right away in those
>> videos.
>> > > > >
>> > > > >
>> > > > >
>> > > > > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <
>> > cjolivier01@gmail.com>
>> > > > > wrote:
>> > > > > > Just curious why you think it’s a bad idea — you didn’t say?
>> > > > > >
>> > > > > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <chenhy12345@gmail.com
>> >
>> > > > wrote:
>> > > > > >
>> > > > > >> At least people needs a way to speak it.
>> > > > > >> Just define its pronunciation as "mix-net" or "m-x-net" and use
>> > the
>> > > > > agreed
>> > > > > >> one everywhere helps a lot.
>> > > > > >> Changing name is a bad idea.
>> > > > > >>
>> > > > > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
>> > > > > >>
>> > > > > >> > Agree that MXNet, the combination of Minerva and CXXNet,
>> which
>> > can
>> > > > be
>> > > > > >> > interpreted as mixed-net, is hard to be pronounced. But
>> > > rebranding a
>> > > > > name
>> > > > > >> > is a very big decision. We need a very carefully designed
>> > > marketing
>> > > > > plan
>> > > > > >> > for it.
>> > > > > >> >
>> > > > > >> > A choice is that we can gradually refer MXNet as a backend,
>> and
>> > > talk
>> > > > > more
>> > > > > >> > about the frontend Gluon.
>> > > > > >> >
>> > > > > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
>> > > > > >> > thomas.delteil1@gmail.com>
>> > > > > >> > wrote:
>> > > > > >> >
>> > > > > >> > > FWIW Brainscript is actually a network definition language:
>> > > > > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
>> > > > > >> > > BrainScript-Network-Builder
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > > Thomas
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <
>> pluskid@gmail.com>:
>> > > > > >> > >
>> > > > > >> > > > IIRC CNTK renamed to something like brainscript which
>> does
>> > not
>> > > > > seem
>> > > > > >> to
>> > > > > >> > be
>> > > > > >> > > > very successful publicity campaign?
>> > > > > >> > > >
>> > > > > >> > > > Chiyuan
>> > > > > >> > > >
>> > > > > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
>> > > > > >> cjolivier01@gmail.com>
>> > > > > >> > > > wrote:
>> > > > > >> > > >
>> > > > > >> > > > > Should we consider renaming MXNet to something more
>> > > > "friendly"?
>> > > > > >> > > > >
>> > > > > >> > > > > IMHO, I think this may be related to adoption problems.
>> > > > > >> > > > >
>> > > > > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to
>> use,
>> > > > don't
>> > > > > >> they?
>> > > > > >> > > > >
>> > > > > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
>> > > > > >> > > > >
>> > > > > >> > > > --
>> > > > > >> > > > Semt ftom m ipohne
>> > > > > >> > > >
>> > > > > >> > >
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > > >> --
>> > > > > >> Chen Hanyang 陈涵洋
>> > > > > >> Software School Fudan University
>> > > > > >> +86-138-1881-7745
>> > > > > >>
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Rahul Huilgol
>> > > >
>> > >
>> >
>>
>
Re: MXNet Name Change?
Posted by xinfan meng <mx...@gmail.com>.
Not sure about changing name. But for branding, how about designing a
mascot? No other frameworks have one yet.
On Wed, 11 Apr 2018 at 23:01, Anirudh <an...@gmail.com> wrote:
> Release naming sounds like a great idea. But we would need this for the
> minor releases too, since many of our customers seem to be switching
> between different minor releases.
>
> On Wed, Apr 11, 2018 at 2:39 PM, Chris Olivier <cj...@gmail.com>
> wrote:
>
> > Ha! good one, Ly!
> > Let's not forget, though, a high percentage of us know who Sean Combs
> is. I
> > couldn't tell you one of his songs, his name changes were a
> differentiator.
> >
> > Makes me think of something -- still another possibility could be the
> > naming of major releases. Like Android does, for instance. "MXNet Alien",
> > for instance for 2.0 (alien just being an example since my home PC is an
> > Alienware). No one else is doing that and it doesnt make me think of
> > something uncomfortable like "M-X-Net" does by itself.
> >
> >
> > On Wed, Apr 11, 2018 at 2:21 PM Ly Nguyen <ng...@gmail.com> wrote:
> >
> > > I agree with comments on not breaking momentum by rebranding the name.
> > It's
> > > also my first time hearing about the pronunciation being "mixnet" and
> not
> > > "m-x-net" so that clarification, along with the motivation behind the
> > name,
> > > feature parity, would strengthen the brand more.
> > >
> > > To that point, Sean Comb's evolution of 5 different names was more
> > > confusing than it was helpful. :)
> > >
> > > On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol <rahulhuilgol@gmail.com
> >
> > > wrote:
> > >
> > > > Even changing the pronunciation is not an easy thing to do IMHO. As
> > > someone
> > > > who has been working on MXNet for the last 8 months, this thread is
> the
> > > > first time I am reading that MXNet is supposed to be pronounced
> > > 'mix-net'.
> > > > We risk losing the momentum even if we try to steer the pronunciation
> > > > towards something which is not popular currently.
> > > >
> > > > I agree Gluon is a friendlier/cooler name. But since we are trying to
> > > > present Gluon as an interface which multiple frameworks can
> implement,
> > > I'm
> > > > not sure if we should try to shift the focus away from MXNet and
> > towards
> > > > Gluon.
> > > >
> > > > As far as adoption goes, I agree with Christopher that public
> > benchmarks
> > > or
> > > > blog posts about how MXNet is better or more usable than other
> > frameworks
> > > > would be worth spending effort on. Rebranding in a way to not lose
> the
> > > > existing momentum honestly sounds more difficult than this :)
> > > >
> > > > By the way, we had some talk of a new friendlier logo sometime back.
> > What
> > > > happened to that?
> > > >
> > > > On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <
> > > aaron.s.markham@gmail.com>
> > > > wrote:
> > > >
> > > > > Changing branding is hard as we already have some momentum under
> the
> > > > > current name. It's not impossible, and if someone has a fantastic
> > idea
> > > > > and marketing plan for it, it's worth considering.
> > > > >
> > > > > Aside from that, updating the pronunciation could be useful if you
> > > > > like having those gif vs jif debates, but at least people would be
> > > > > talking about it. I personally like the sound of "mix-net" over
> > > > > "em-ex-net". Since we're just starting Youtube videos, I think
> it's a
> > > > > great idea to establish the pronunciation right away in those
> videos.
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <
> > cjolivier01@gmail.com>
> > > > > wrote:
> > > > > > Just curious why you think it’s a bad idea — you didn’t say?
> > > > > >
> > > > > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > >> At least people needs a way to speak it.
> > > > > >> Just define its pronunciation as "mix-net" or "m-x-net" and use
> > the
> > > > > agreed
> > > > > >> one everywhere helps a lot.
> > > > > >> Changing name is a bad idea.
> > > > > >>
> > > > > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> > > > > >>
> > > > > >> > Agree that MXNet, the combination of Minerva and CXXNet, which
> > can
> > > > be
> > > > > >> > interpreted as mixed-net, is hard to be pronounced. But
> > > rebranding a
> > > > > name
> > > > > >> > is a very big decision. We need a very carefully designed
> > > marketing
> > > > > plan
> > > > > >> > for it.
> > > > > >> >
> > > > > >> > A choice is that we can gradually refer MXNet as a backend,
> and
> > > talk
> > > > > more
> > > > > >> > about the frontend Gluon.
> > > > > >> >
> > > > > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > > > > >> > thomas.delteil1@gmail.com>
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> > > FWIW Brainscript is actually a network definition language:
> > > > > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > > > > >> > > BrainScript-Network-Builder
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > Thomas
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pluskid@gmail.com
> >:
> > > > > >> > >
> > > > > >> > > > IIRC CNTK renamed to something like brainscript which does
> > not
> > > > > seem
> > > > > >> to
> > > > > >> > be
> > > > > >> > > > very successful publicity campaign?
> > > > > >> > > >
> > > > > >> > > > Chiyuan
> > > > > >> > > >
> > > > > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > > > > >> cjolivier01@gmail.com>
> > > > > >> > > > wrote:
> > > > > >> > > >
> > > > > >> > > > > Should we consider renaming MXNet to something more
> > > > "friendly"?
> > > > > >> > > > >
> > > > > >> > > > > IMHO, I think this may be related to adoption problems.
> > > > > >> > > > >
> > > > > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to
> use,
> > > > don't
> > > > > >> they?
> > > > > >> > > > >
> > > > > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > > > > >> > > > >
> > > > > >> > > > --
> > > > > >> > > > Semt ftom m ipohne
> > > > > >> > > >
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Chen Hanyang 陈涵洋
> > > > > >> Software School Fudan University
> > > > > >> +86-138-1881-7745
> > > > > >>
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Rahul Huilgol
> > > >
> > >
> >
>
Re: MXNet Name Change?
Posted by Anirudh <an...@gmail.com>.
Release naming sounds like a great idea. But we would need this for the
minor releases too, since many of our customers seem to be switching
between different minor releases.
On Wed, Apr 11, 2018 at 2:39 PM, Chris Olivier <cj...@gmail.com>
wrote:
> Ha! good one, Ly!
> Let's not forget, though, a high percentage of us know who Sean Combs is. I
> couldn't tell you one of his songs, his name changes were a differentiator.
>
> Makes me think of something -- still another possibility could be the
> naming of major releases. Like Android does, for instance. "MXNet Alien",
> for instance for 2.0 (alien just being an example since my home PC is an
> Alienware). No one else is doing that and it doesnt make me think of
> something uncomfortable like "M-X-Net" does by itself.
>
>
> On Wed, Apr 11, 2018 at 2:21 PM Ly Nguyen <ng...@gmail.com> wrote:
>
> > I agree with comments on not breaking momentum by rebranding the name.
> It's
> > also my first time hearing about the pronunciation being "mixnet" and not
> > "m-x-net" so that clarification, along with the motivation behind the
> name,
> > feature parity, would strengthen the brand more.
> >
> > To that point, Sean Comb's evolution of 5 different names was more
> > confusing than it was helpful. :)
> >
> > On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol <ra...@gmail.com>
> > wrote:
> >
> > > Even changing the pronunciation is not an easy thing to do IMHO. As
> > someone
> > > who has been working on MXNet for the last 8 months, this thread is the
> > > first time I am reading that MXNet is supposed to be pronounced
> > 'mix-net'.
> > > We risk losing the momentum even if we try to steer the pronunciation
> > > towards something which is not popular currently.
> > >
> > > I agree Gluon is a friendlier/cooler name. But since we are trying to
> > > present Gluon as an interface which multiple frameworks can implement,
> > I'm
> > > not sure if we should try to shift the focus away from MXNet and
> towards
> > > Gluon.
> > >
> > > As far as adoption goes, I agree with Christopher that public
> benchmarks
> > or
> > > blog posts about how MXNet is better or more usable than other
> frameworks
> > > would be worth spending effort on. Rebranding in a way to not lose the
> > > existing momentum honestly sounds more difficult than this :)
> > >
> > > By the way, we had some talk of a new friendlier logo sometime back.
> What
> > > happened to that?
> > >
> > > On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <
> > aaron.s.markham@gmail.com>
> > > wrote:
> > >
> > > > Changing branding is hard as we already have some momentum under the
> > > > current name. It's not impossible, and if someone has a fantastic
> idea
> > > > and marketing plan for it, it's worth considering.
> > > >
> > > > Aside from that, updating the pronunciation could be useful if you
> > > > like having those gif vs jif debates, but at least people would be
> > > > talking about it. I personally like the sound of "mix-net" over
> > > > "em-ex-net". Since we're just starting Youtube videos, I think it's a
> > > > great idea to establish the pronunciation right away in those videos.
> > > >
> > > >
> > > >
> > > > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <
> cjolivier01@gmail.com>
> > > > wrote:
> > > > > Just curious why you think it’s a bad idea — you didn’t say?
> > > > >
> > > > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com>
> > > wrote:
> > > > >
> > > > >> At least people needs a way to speak it.
> > > > >> Just define its pronunciation as "mix-net" or "m-x-net" and use
> the
> > > > agreed
> > > > >> one everywhere helps a lot.
> > > > >> Changing name is a bad idea.
> > > > >>
> > > > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> > > > >>
> > > > >> > Agree that MXNet, the combination of Minerva and CXXNet, which
> can
> > > be
> > > > >> > interpreted as mixed-net, is hard to be pronounced. But
> > rebranding a
> > > > name
> > > > >> > is a very big decision. We need a very carefully designed
> > marketing
> > > > plan
> > > > >> > for it.
> > > > >> >
> > > > >> > A choice is that we can gradually refer MXNet as a backend, and
> > talk
> > > > more
> > > > >> > about the frontend Gluon.
> > > > >> >
> > > > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > > > >> > thomas.delteil1@gmail.com>
> > > > >> > wrote:
> > > > >> >
> > > > >> > > FWIW Brainscript is actually a network definition language:
> > > > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > > > >> > > BrainScript-Network-Builder
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > Thomas
> > > > >> > >
> > > > >> > >
> > > > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> > > > >> > >
> > > > >> > > > IIRC CNTK renamed to something like brainscript which does
> not
> > > > seem
> > > > >> to
> > > > >> > be
> > > > >> > > > very successful publicity campaign?
> > > > >> > > >
> > > > >> > > > Chiyuan
> > > > >> > > >
> > > > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > > > >> cjolivier01@gmail.com>
> > > > >> > > > wrote:
> > > > >> > > >
> > > > >> > > > > Should we consider renaming MXNet to something more
> > > "friendly"?
> > > > >> > > > >
> > > > >> > > > > IMHO, I think this may be related to adoption problems.
> > > > >> > > > >
> > > > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use,
> > > don't
> > > > >> they?
> > > > >> > > > >
> > > > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > > > >> > > > >
> > > > >> > > > --
> > > > >> > > > Semt ftom m ipohne
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Chen Hanyang 陈涵洋
> > > > >> Software School Fudan University
> > > > >> +86-138-1881-7745
> > > > >>
> > > >
> > >
> > >
> > >
> > > --
> > > Rahul Huilgol
> > >
> >
>
Re: MXNet Name Change?
Posted by Chris Olivier <cj...@gmail.com>.
Ha! good one, Ly!
Let's not forget, though, a high percentage of us know who Sean Combs is. I
couldn't tell you one of his songs, his name changes were a differentiator.
Makes me think of something -- still another possibility could be the
naming of major releases. Like Android does, for instance. "MXNet Alien",
for instance for 2.0 (alien just being an example since my home PC is an
Alienware). No one else is doing that and it doesnt make me think of
something uncomfortable like "M-X-Net" does by itself.
On Wed, Apr 11, 2018 at 2:21 PM Ly Nguyen <ng...@gmail.com> wrote:
> I agree with comments on not breaking momentum by rebranding the name. It's
> also my first time hearing about the pronunciation being "mixnet" and not
> "m-x-net" so that clarification, along with the motivation behind the name,
> feature parity, would strengthen the brand more.
>
> To that point, Sean Comb's evolution of 5 different names was more
> confusing than it was helpful. :)
>
> On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol <ra...@gmail.com>
> wrote:
>
> > Even changing the pronunciation is not an easy thing to do IMHO. As
> someone
> > who has been working on MXNet for the last 8 months, this thread is the
> > first time I am reading that MXNet is supposed to be pronounced
> 'mix-net'.
> > We risk losing the momentum even if we try to steer the pronunciation
> > towards something which is not popular currently.
> >
> > I agree Gluon is a friendlier/cooler name. But since we are trying to
> > present Gluon as an interface which multiple frameworks can implement,
> I'm
> > not sure if we should try to shift the focus away from MXNet and towards
> > Gluon.
> >
> > As far as adoption goes, I agree with Christopher that public benchmarks
> or
> > blog posts about how MXNet is better or more usable than other frameworks
> > would be worth spending effort on. Rebranding in a way to not lose the
> > existing momentum honestly sounds more difficult than this :)
> >
> > By the way, we had some talk of a new friendlier logo sometime back. What
> > happened to that?
> >
> > On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <
> aaron.s.markham@gmail.com>
> > wrote:
> >
> > > Changing branding is hard as we already have some momentum under the
> > > current name. It's not impossible, and if someone has a fantastic idea
> > > and marketing plan for it, it's worth considering.
> > >
> > > Aside from that, updating the pronunciation could be useful if you
> > > like having those gif vs jif debates, but at least people would be
> > > talking about it. I personally like the sound of "mix-net" over
> > > "em-ex-net". Since we're just starting Youtube videos, I think it's a
> > > great idea to establish the pronunciation right away in those videos.
> > >
> > >
> > >
> > > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com>
> > > wrote:
> > > > Just curious why you think it’s a bad idea — you didn’t say?
> > > >
> > > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com>
> > wrote:
> > > >
> > > >> At least people needs a way to speak it.
> > > >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> > > agreed
> > > >> one everywhere helps a lot.
> > > >> Changing name is a bad idea.
> > > >>
> > > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> > > >>
> > > >> > Agree that MXNet, the combination of Minerva and CXXNet, which can
> > be
> > > >> > interpreted as mixed-net, is hard to be pronounced. But
> rebranding a
> > > name
> > > >> > is a very big decision. We need a very carefully designed
> marketing
> > > plan
> > > >> > for it.
> > > >> >
> > > >> > A choice is that we can gradually refer MXNet as a backend, and
> talk
> > > more
> > > >> > about the frontend Gluon.
> > > >> >
> > > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > > >> > thomas.delteil1@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > FWIW Brainscript is actually a network definition language:
> > > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > > >> > > BrainScript-Network-Builder
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > Thomas
> > > >> > >
> > > >> > >
> > > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> > > >> > >
> > > >> > > > IIRC CNTK renamed to something like brainscript which does not
> > > seem
> > > >> to
> > > >> > be
> > > >> > > > very successful publicity campaign?
> > > >> > > >
> > > >> > > > Chiyuan
> > > >> > > >
> > > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > > >> cjolivier01@gmail.com>
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > > > Should we consider renaming MXNet to something more
> > "friendly"?
> > > >> > > > >
> > > >> > > > > IMHO, I think this may be related to adoption problems.
> > > >> > > > >
> > > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use,
> > don't
> > > >> they?
> > > >> > > > >
> > > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > > >> > > > >
> > > >> > > > --
> > > >> > > > Semt ftom m ipohne
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Chen Hanyang 陈涵洋
> > > >> Software School Fudan University
> > > >> +86-138-1881-7745
> > > >>
> > >
> >
> >
> >
> > --
> > Rahul Huilgol
> >
>
Re: MXNet Name Change?
Posted by Ly Nguyen <ng...@gmail.com>.
I agree with comments on not breaking momentum by rebranding the name. It's
also my first time hearing about the pronunciation being "mixnet" and not
"m-x-net" so that clarification, along with the motivation behind the name,
feature parity, would strengthen the brand more.
To that point, Sean Comb's evolution of 5 different names was more
confusing than it was helpful. :)
On Wed, Apr 11, 2018 at 1:58 PM, Rahul Huilgol <ra...@gmail.com>
wrote:
> Even changing the pronunciation is not an easy thing to do IMHO. As someone
> who has been working on MXNet for the last 8 months, this thread is the
> first time I am reading that MXNet is supposed to be pronounced 'mix-net'.
> We risk losing the momentum even if we try to steer the pronunciation
> towards something which is not popular currently.
>
> I agree Gluon is a friendlier/cooler name. But since we are trying to
> present Gluon as an interface which multiple frameworks can implement, I'm
> not sure if we should try to shift the focus away from MXNet and towards
> Gluon.
>
> As far as adoption goes, I agree with Christopher that public benchmarks or
> blog posts about how MXNet is better or more usable than other frameworks
> would be worth spending effort on. Rebranding in a way to not lose the
> existing momentum honestly sounds more difficult than this :)
>
> By the way, we had some talk of a new friendlier logo sometime back. What
> happened to that?
>
> On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <aa...@gmail.com>
> wrote:
>
> > Changing branding is hard as we already have some momentum under the
> > current name. It's not impossible, and if someone has a fantastic idea
> > and marketing plan for it, it's worth considering.
> >
> > Aside from that, updating the pronunciation could be useful if you
> > like having those gif vs jif debates, but at least people would be
> > talking about it. I personally like the sound of "mix-net" over
> > "em-ex-net". Since we're just starting Youtube videos, I think it's a
> > great idea to establish the pronunciation right away in those videos.
> >
> >
> >
> > On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com>
> > wrote:
> > > Just curious why you think it’s a bad idea — you didn’t say?
> > >
> > > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com>
> wrote:
> > >
> > >> At least people needs a way to speak it.
> > >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> > agreed
> > >> one everywhere helps a lot.
> > >> Changing name is a bad idea.
> > >>
> > >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> > >>
> > >> > Agree that MXNet, the combination of Minerva and CXXNet, which can
> be
> > >> > interpreted as mixed-net, is hard to be pronounced. But rebranding a
> > name
> > >> > is a very big decision. We need a very carefully designed marketing
> > plan
> > >> > for it.
> > >> >
> > >> > A choice is that we can gradually refer MXNet as a backend, and talk
> > more
> > >> > about the frontend Gluon.
> > >> >
> > >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > >> > thomas.delteil1@gmail.com>
> > >> > wrote:
> > >> >
> > >> > > FWIW Brainscript is actually a network definition language:
> > >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > >> > > BrainScript-Network-Builder
> > >> > >
> > >> > >
> > >> > >
> > >> > > Thomas
> > >> > >
> > >> > >
> > >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> > >> > >
> > >> > > > IIRC CNTK renamed to something like brainscript which does not
> > seem
> > >> to
> > >> > be
> > >> > > > very successful publicity campaign?
> > >> > > >
> > >> > > > Chiyuan
> > >> > > >
> > >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> > >> cjolivier01@gmail.com>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Should we consider renaming MXNet to something more
> "friendly"?
> > >> > > > >
> > >> > > > > IMHO, I think this may be related to adoption problems.
> > >> > > > >
> > >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use,
> don't
> > >> they?
> > >> > > > >
> > >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > >> > > > >
> > >> > > > --
> > >> > > > Semt ftom m ipohne
> > >> > > >
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Chen Hanyang 陈涵洋
> > >> Software School Fudan University
> > >> +86-138-1881-7745
> > >>
> >
>
>
>
> --
> Rahul Huilgol
>
Re: MXNet Name Change?
Posted by Rahul Huilgol <ra...@gmail.com>.
Even changing the pronunciation is not an easy thing to do IMHO. As someone
who has been working on MXNet for the last 8 months, this thread is the
first time I am reading that MXNet is supposed to be pronounced 'mix-net'.
We risk losing the momentum even if we try to steer the pronunciation
towards something which is not popular currently.
I agree Gluon is a friendlier/cooler name. But since we are trying to
present Gluon as an interface which multiple frameworks can implement, I'm
not sure if we should try to shift the focus away from MXNet and towards
Gluon.
As far as adoption goes, I agree with Christopher that public benchmarks or
blog posts about how MXNet is better or more usable than other frameworks
would be worth spending effort on. Rebranding in a way to not lose the
existing momentum honestly sounds more difficult than this :)
By the way, we had some talk of a new friendlier logo sometime back. What
happened to that?
On Wed, Apr 11, 2018 at 1:43 PM, Aaron Markham <aa...@gmail.com>
wrote:
> Changing branding is hard as we already have some momentum under the
> current name. It's not impossible, and if someone has a fantastic idea
> and marketing plan for it, it's worth considering.
>
> Aside from that, updating the pronunciation could be useful if you
> like having those gif vs jif debates, but at least people would be
> talking about it. I personally like the sound of "mix-net" over
> "em-ex-net". Since we're just starting Youtube videos, I think it's a
> great idea to establish the pronunciation right away in those videos.
>
>
>
> On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com>
> wrote:
> > Just curious why you think it’s a bad idea — you didn’t say?
> >
> > On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com> wrote:
> >
> >> At least people needs a way to speak it.
> >> Just define its pronunciation as "mix-net" or "m-x-net" and use the
> agreed
> >> one everywhere helps a lot.
> >> Changing name is a bad idea.
> >>
> >> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> >>
> >> > Agree that MXNet, the combination of Minerva and CXXNet, which can be
> >> > interpreted as mixed-net, is hard to be pronounced. But rebranding a
> name
> >> > is a very big decision. We need a very carefully designed marketing
> plan
> >> > for it.
> >> >
> >> > A choice is that we can gradually refer MXNet as a backend, and talk
> more
> >> > about the frontend Gluon.
> >> >
> >> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> >> > thomas.delteil1@gmail.com>
> >> > wrote:
> >> >
> >> > > FWIW Brainscript is actually a network definition language:
> >> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> >> > > BrainScript-Network-Builder
> >> > >
> >> > >
> >> > >
> >> > > Thomas
> >> > >
> >> > >
> >> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> >> > >
> >> > > > IIRC CNTK renamed to something like brainscript which does not
> seem
> >> to
> >> > be
> >> > > > very successful publicity campaign?
> >> > > >
> >> > > > Chiyuan
> >> > > >
> >> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> >> cjolivier01@gmail.com>
> >> > > > wrote:
> >> > > >
> >> > > > > Should we consider renaming MXNet to something more "friendly"?
> >> > > > >
> >> > > > > IMHO, I think this may be related to adoption problems.
> >> > > > >
> >> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't
> >> they?
> >> > > > >
> >> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> >> > > > >
> >> > > > --
> >> > > > Semt ftom m ipohne
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Chen Hanyang 陈涵洋
> >> Software School Fudan University
> >> +86-138-1881-7745
> >>
>
--
Rahul Huilgol
Re: MXNet Name Change?
Posted by Aaron Markham <aa...@gmail.com>.
Changing branding is hard as we already have some momentum under the
current name. It's not impossible, and if someone has a fantastic idea
and marketing plan for it, it's worth considering.
Aside from that, updating the pronunciation could be useful if you
like having those gif vs jif debates, but at least people would be
talking about it. I personally like the sound of "mix-net" over
"em-ex-net". Since we're just starting Youtube videos, I think it's a
great idea to establish the pronunciation right away in those videos.
On Wed, Apr 11, 2018 at 1:33 PM, Chris Olivier <cj...@gmail.com> wrote:
> Just curious why you think it’s a bad idea — you didn’t say?
>
> On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com> wrote:
>
>> At least people needs a way to speak it.
>> Just define its pronunciation as "mix-net" or "m-x-net" and use the agreed
>> one everywhere helps a lot.
>> Changing name is a bad idea.
>>
>> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
>>
>> > Agree that MXNet, the combination of Minerva and CXXNet, which can be
>> > interpreted as mixed-net, is hard to be pronounced. But rebranding a name
>> > is a very big decision. We need a very carefully designed marketing plan
>> > for it.
>> >
>> > A choice is that we can gradually refer MXNet as a backend, and talk more
>> > about the frontend Gluon.
>> >
>> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
>> > thomas.delteil1@gmail.com>
>> > wrote:
>> >
>> > > FWIW Brainscript is actually a network definition language:
>> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
>> > > BrainScript-Network-Builder
>> > >
>> > >
>> > >
>> > > Thomas
>> > >
>> > >
>> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
>> > >
>> > > > IIRC CNTK renamed to something like brainscript which does not seem
>> to
>> > be
>> > > > very successful publicity campaign?
>> > > >
>> > > > Chiyuan
>> > > >
>> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
>> cjolivier01@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > Should we consider renaming MXNet to something more "friendly"?
>> > > > >
>> > > > > IMHO, I think this may be related to adoption problems.
>> > > > >
>> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't
>> they?
>> > > > >
>> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
>> > > > >
>> > > > --
>> > > > Semt ftom m ipohne
>> > > >
>> > >
>> >
>>
>>
>>
>> --
>> Chen Hanyang 陈涵洋
>> Software School Fudan University
>> +86-138-1881-7745
>>
Re: MXNet Name Change?
Posted by Chris Olivier <cj...@gmail.com>.
Just curious why you think it’s a bad idea — you didn’t say?
On Wed, Apr 11, 2018 at 12:49 PM Chen HY <ch...@gmail.com> wrote:
> At least people needs a way to speak it.
> Just define its pronunciation as "mix-net" or "m-x-net" and use the agreed
> one everywhere helps a lot.
> Changing name is a bad idea.
>
> 2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
>
> > Agree that MXNet, the combination of Minerva and CXXNet, which can be
> > interpreted as mixed-net, is hard to be pronounced. But rebranding a name
> > is a very big decision. We need a very carefully designed marketing plan
> > for it.
> >
> > A choice is that we can gradually refer MXNet as a backend, and talk more
> > about the frontend Gluon.
> >
> > On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> > thomas.delteil1@gmail.com>
> > wrote:
> >
> > > FWIW Brainscript is actually a network definition language:
> > > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > > BrainScript-Network-Builder
> > >
> > >
> > >
> > > Thomas
> > >
> > >
> > > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> > >
> > > > IIRC CNTK renamed to something like brainscript which does not seem
> to
> > be
> > > > very successful publicity campaign?
> > > >
> > > > Chiyuan
> > > >
> > > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <
> cjolivier01@gmail.com>
> > > > wrote:
> > > >
> > > > > Should we consider renaming MXNet to something more "friendly"?
> > > > >
> > > > > IMHO, I think this may be related to adoption problems.
> > > > >
> > > > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't
> they?
> > > > >
> > > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > > > >
> > > > --
> > > > Semt ftom m ipohne
> > > >
> > >
> >
>
>
>
> --
> Chen Hanyang 陈涵洋
> Software School Fudan University
> +86-138-1881-7745
>
Re: MXNet Name Change?
Posted by Chen HY <ch...@gmail.com>.
At least people needs a way to speak it.
Just define its pronunciation as "mix-net" or "m-x-net" and use the agreed
one everywhere helps a lot.
Changing name is a bad idea.
2018-04-11 20:29 GMT+01:00 Mu Li <mu...@gmail.com>:
> Agree that MXNet, the combination of Minerva and CXXNet, which can be
> interpreted as mixed-net, is hard to be pronounced. But rebranding a name
> is a very big decision. We need a very carefully designed marketing plan
> for it.
>
> A choice is that we can gradually refer MXNet as a backend, and talk more
> about the frontend Gluon.
>
> On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <
> thomas.delteil1@gmail.com>
> wrote:
>
> > FWIW Brainscript is actually a network definition language:
> > https://docs.microsoft.com/en-us/cognitive-toolkit/
> > BrainScript-Network-Builder
> >
> >
> >
> > Thomas
> >
> >
> > 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> >
> > > IIRC CNTK renamed to something like brainscript which does not seem to
> be
> > > very successful publicity campaign?
> > >
> > > Chiyuan
> > >
> > > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <cj...@gmail.com>
> > > wrote:
> > >
> > > > Should we consider renaming MXNet to something more "friendly"?
> > > >
> > > > IMHO, I think this may be related to adoption problems.
> > > >
> > > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
> > > >
> > > > Tensorflow, PyTorch, Caffe -- sound cool.
> > > >
> > > --
> > > Semt ftom m ipohne
> > >
> >
>
--
Chen Hanyang 陈涵洋
Software School Fudan University
+86-138-1881-7745
Re: MXNet Name Change?
Posted by Mu Li <mu...@gmail.com>.
Agree that MXNet, the combination of Minerva and CXXNet, which can be
interpreted as mixed-net, is hard to be pronounced. But rebranding a name
is a very big decision. We need a very carefully designed marketing plan
for it.
A choice is that we can gradually refer MXNet as a backend, and talk more
about the frontend Gluon.
On Wed, Apr 11, 2018 at 12:16 PM, Thomas DELTEIL <th...@gmail.com>
wrote:
> FWIW Brainscript is actually a network definition language:
> https://docs.microsoft.com/en-us/cognitive-toolkit/
> BrainScript-Network-Builder
>
>
>
> Thomas
>
>
> 2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
>
> > IIRC CNTK renamed to something like brainscript which does not seem to be
> > very successful publicity campaign?
> >
> > Chiyuan
> >
> > On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <cj...@gmail.com>
> > wrote:
> >
> > > Should we consider renaming MXNet to something more "friendly"?
> > >
> > > IMHO, I think this may be related to adoption problems.
> > >
> > > MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
> > >
> > > Tensorflow, PyTorch, Caffe -- sound cool.
> > >
> > --
> > Semt ftom m ipohne
> >
>
Re: MXNet Name Change?
Posted by Thomas DELTEIL <th...@gmail.com>.
FWIW Brainscript is actually a network definition language:
https://docs.microsoft.com/en-us/cognitive-toolkit/BrainScript-Network-Builder
Thomas
2018-04-11 12:13 GMT-07:00 Chiyuan Zhang <pl...@gmail.com>:
> IIRC CNTK renamed to something like brainscript which does not seem to be
> very successful publicity campaign?
>
> Chiyuan
>
> On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <cj...@gmail.com>
> wrote:
>
> > Should we consider renaming MXNet to something more "friendly"?
> >
> > IMHO, I think this may be related to adoption problems.
> >
> > MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
> >
> > Tensorflow, PyTorch, Caffe -- sound cool.
> >
> --
> Semt ftom m ipohne
>
Re: MXNet Name Change?
Posted by Chiyuan Zhang <pl...@gmail.com>.
IIRC CNTK renamed to something like brainscript which does not seem to be
very successful publicity campaign?
Chiyuan
On Wed, Apr 11, 2018 at 10:18 AM Chris Olivier <cj...@gmail.com>
wrote:
> Should we consider renaming MXNet to something more "friendly"?
>
> IMHO, I think this may be related to adoption problems.
>
> MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
>
> Tensorflow, PyTorch, Caffe -- sound cool.
>
--
Semt ftom m ipohne
Re: MXNet Name Change?
Posted by "Barber, Christopher" <Ch...@analog.com>.
While the name could be better, I would instead focus on (1) making mxnet much more extensible (e.g. support ability to dynamically load operators from external shared libraries), (2) feature parity with tensorflow, (3) support for non-NVIDIA GPUs, (4) clearly demonstrating and publicizing better performance for large models.
On 4/11/18, 1:18 PM, "Chris Olivier" <cj...@gmail.com> wrote:
Should we consider renaming MXNet to something more "friendly"?
IMHO, I think this may be related to adoption problems.
MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
Tensorflow, PyTorch, Caffe -- sound cool.
Re: MXNet Name Change?
Posted by "Singh, Rajan" <sr...@amazon.com>.
I agree with Anirudh about the confusion with the name.
Also, if someone hasn’t heard about "MXNet" , they could confuse it with another model like "AlexNet", "GoogleNet"
Not sure about the feasibility of doing it at this point .
On 4/11/18, 11:10 AM, "Anirudh" <an...@gmail.com> wrote:
Hi Chris,
In my opinion, the problem with MXNet is the way it is pronounced. I think
this leads to confusion, as I have seen people unaware of the fw from
before, grasp it as "Amexnet". The way it was supposed to be pronounced
"mixnet" sounded like a good name to me. I am not sure why the i in the
middle was removed though.
Having said that, I don't think it would be feasible to change the name at
this stage, considering the confusion and the marketing nightmare. I cannot
recall of other popular open source projects of having changed their names
without an impact.
Anirudh
On Wed, Apr 11, 2018 at 10:18 AM, Chris Olivier <cj...@gmail.com>
wrote:
> Should we consider renaming MXNet to something more "friendly"?
>
> IMHO, I think this may be related to adoption problems.
>
> MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
>
> Tensorflow, PyTorch, Caffe -- sound cool.
>
Re: MXNet Name Change?
Posted by Anirudh <an...@gmail.com>.
Hi Chris,
In my opinion, the problem with MXNet is the way it is pronounced. I think
this leads to confusion, as I have seen people unaware of the fw from
before, grasp it as "Amexnet". The way it was supposed to be pronounced
"mixnet" sounded like a good name to me. I am not sure why the i in the
middle was removed though.
Having said that, I don't think it would be feasible to change the name at
this stage, considering the confusion and the marketing nightmare. I cannot
recall of other popular open source projects of having changed their names
without an impact.
Anirudh
On Wed, Apr 11, 2018 at 10:18 AM, Chris Olivier <cj...@gmail.com>
wrote:
> Should we consider renaming MXNet to something more "friendly"?
>
> IMHO, I think this may be related to adoption problems.
>
> MXNet, CMTK -- both seem sort of sterile and hard to use, don't they?
>
> Tensorflow, PyTorch, Caffe -- sound cool.
>