ied is looking for a better name! about ied HOT 63 OPEN

Let's name it kik. Three letters, easy to spell. Not sure if I'm serious...

/cc @azer

from ied.

mopp (manage our packages please)

from ied.

How about nom?

There's an extant npm package but it looks like it might be abandonware. Maybe @matthewmueller would be willing to let it go.

from ied.

Also, I would be extremely disappointed if nom wasn't an alias for install:

nom nom mocha

from ied.

I still think that nom is the most likely to have the most adoption.

Makes me think of pacman and cute eating creatures

from ied.

Sounds good :-) I've gone ahead and given you publishing rights to nom. Feel free to overwrite it when you're ready to go.

from ied.

+1 for nom

from ied.

I love nom, it is cute and it is very close to npm too. Also +1 on nom nom as an alias for install

from ied.

So… any chance of this rename happening?

from ied.

Just for fun: mom

Manager of Modules

"Let Mom do it for you!"

mom install # my stuff for me
mom start # my project
mom test # what I've learned
mom cook # alias for mom install && mom start

from ied.

At least you know nobody will ever come to steal you name ;)

from ied.

pmn sounds good, but I'm a bit worried about the m and n next to each other. pmn sounds very similar to pnm. It also looks very similar, especially when written in a monospace font I think....

I also don't know if it's intentional that pmn is an anagram of npm, but it's kind of cool for sure.

from ied.

I kind of like the name ied, despite the connotation,,reminds me of 'ed'. Perhaps you could pronounce it like aye-ed or ee-ed or yi-ed

from ied.

Same here.

from ied.

ya, pretty loaded name :|

from ied.

So there is actually an existing issue for this at #14 where the conversation gets locked.

@alexanderGugel Perhaps under in the README where you discuss the name you should change the paragraph from Nothing in particular (which could be mistakenly understood for the original definition) and explain that the project is looking for a new name?

from ied.

This is not the first time this comes up: #27, #25, #14, HN.

So let's have this discussion. I renamed the issue.

Constructive comments only, please. I originally said that I would rename ied as soon as I decided on a better name. This hasn't happened, yet. I closed all previous issues because I wanted to avoid a giant discussion without any meaningful results and with personal insults as a consequence.

I won't hesitate to delete comments or lock this issue. Insulting comments will be deleted, but also replies that don't contribute to the discussion in any meaningful way (this includes personal experiences and situations of family members - while they may be sad, those stories do not belong here). I know this might feel insulting, but I would really like to end this discussion in the most efficient way possible.

So... if you have a proposal for a better name, please post it here.

@alexanderGugel Perhaps under in the README where you discuss the name you should change the paragraph from Nothing in particular (which could be mistakenly understood for the original definition) and explain that the project is looking for a new name?

Submit a PR if you feel strongly about that.

from ied.

• pm (package manager)
• nnpm (new node package manager)
• epm (ecma package manager)
• xpm (xtreme package manager)
• mm (module manager)
• spm (super package manager)
• bpm (better package manager, "b" is 1 key away from "n")

from ied.

@bcherny Nice suggestions, but only one of them (nnpm) is available on npmjs.com 😢

• pii (Package Installing Improved)
• ufm (Understandably Faster Management)
• cbm (Compiling Beer Modules)
• tai (Type And Install) (I quite like this one) (You can trust Tai!)

(Funny enough, my first though, inpm, is taken by a module that checks to see if names are taken in the NPM repository LOL)

Can I please suggest that anyone looking to suggest a name should check to see if the name is available on npmjs.com to save time re-working an abbreviation when a nice name is found?

from ied.

I suggest asking for mpm. Failing that, I like xpm, which you would also need to ask for. :)

https://www.npmjs.com/policies/disputes

from ied.

pmn isn't taken. (Package Man)

from ied.

jpi - Javascript package installer

not taken

from ied.

@benatkin I emailed the author before, but they didn't respond. I didn't want to reach out to npm, because it seemed slightly aggressive considering the nature of this very project.

from ied.

I would hope you would not find the folks at npm hostile to this project. Working on an alternative implementation is not inherently threatening - their business model does not revolve around usage of their CLI. Seems to me this is much more likely to help them or have negligible impact than hurt.

I'd think requesting mediation about a name would go the same way as it would for anyone else.

from ied.

There are loads of projects about alternative package installers - it doesn't
make this one less valuable or less important, I'm just saying - which I
discovered tonight when searching NPM for other names.

Honestly, they should welcome it. If this project is indeed faster, they should
welcome the input!!

from ied.

Working on an alternative implementation is not inherently threatening - their business model does not revolve around usage of their CLI.

☝️

As long as you follow these guidelines, you should be fine: https://www.npmjs.com/policies/disputes

from ied.

pmn (package manager for node)
https://www.npmjs.com/package/pmn

Oh didn't read all the thread :-/

from ied.

Alright, we've got two for pmn! Anyone else agree? Let's see some thumbs 😃

from ied.

My final suggestion is jmm - JavaScript Module Manager. Take it or leave it.

from ied.

dang this looks awesome. just a quick test on some bigger repos and I found some bugs:

• doesn't work for scoped packages yet (ex. @scope/package) or at least doesn't read from .npmrc:

Unexpected status code 404 for http://registry.npmjs.org/@scope%2Fpackage

• doesn't work with git urls

No satisfying target found for esprima@git://github.com/ariya/esprima.git#harmony

Overall user experience is so much better and it's a lot faster. I'd be down to donate nom to the cause 😄

from ied.

I like pmn too. Simple to write and pronounce...

from ied.

Gotcha on the similarIty between the two.

The anagram kind of was intentional 😄

from ied.

I like xpm and I'd suggest making the binary x

$ x install

rolls off the keyboard really nicely

from ied.

👍 for XPM

I was also thinking about ESB and OPF.

from ied.

👍 on xpm. Stands out.

from ied.

I like XPM. Legit. 👍

from ied.

There might be a couple of naming conflicts though: https://en.wikipedia.org/wiki/XPM

from ied.

LPM - Lean Package Manager
LDM - Lean Dependency Manager
PDM - Project Dependency Manager

lpm is easy to type

from ied.

Another suggestion: NHD - non-humane design.

Before I started working on ied, I asked in the npm IRC channel why npm doesn't do what ied does (in terms of symlinks + CAS). Below is an excerpt of the conversation we had (yes, I logged in as nodejsnoob - because I thought I was missing something obvious, I left out a couple of messages for the sake of brevity):

[...]

[22:38] <nodejsnoob> why can't it be like a CAS, with additional "root-level" symlinks from the actual "real" names?
[22:39] <nodejsnoob> e.g. the checksum of a package would be used as "real" location, while an additional symlink, e.g. `my_package/node_modules/tape` would link to  `my_package/node_modules/[checksum of specific tape version]`

[...]

[22:39] <Aria> A different kind of complexity.
[22:40] == nodejsnoob has changed nick to alexanderGugel
[22:40] <Aria> Also there are a couple non-obvious things about symlinks: node looks for modules in the parent directory of a module's _real_ path.
[22:40] <ljharb> also then it would be hard to modify node modules on the filesystem manually, and have your changes reflected
[22:40] <alexanderGugel> Why? The package.json files from the registry already include the checksum
[22:40] <alexanderGugel> that's true. didn't think of that.
[22:40] <Aria> Yeah, that's a validator for the data. Not an identity for the package.
[22:41] == proudlygeek [[email protected]] has joined #npm
[22:42] <alexanderGugel> Aria: Where is the difference? Can't we assume that the specific version of the package is not going to change?

[...]

And - finally - the quote I've been looking for: "not a humane design"

[22:43] <Aria> Generally, yes. But it's just completely not a humane design. And this is the path of least resistance.

I think that would be a good self-ironic name. Thoughts?

from ied.

While I can appreciate the inspiration, it may push away developers ignorant of the name's context.

from ied.

My 3 yen:

• pmn and pnm are impossible to pronounce or remember.
• Do you really need to stick to 3 letters?
• nom incredibly is awesome. Node version of yum.

from ied.

pmn and pnm are impossible to pronounce or remember.

I kind of agree 😢

• Do you really need to stick to 3 letters?

Yes. I type like a monkey. Everything more than 3 letters is too much of a challenge.

• nom incredibly is awesome. Node version of yum.

Hmmmm.. sounds like some sort of noodles... Or food.... "nomnomnomnomnomnomnomnom"

from ied.

Ha, I also type like a monkey! Left hand for a, s, and space. Right hand for everything else.

Yep, nom nom nom... yum! The memes are endless:

Image caption: nom nom nom -g

from ied.

If you could get permission to use nom, I'd be so down with that.

from ied.

You could call it nom but use omnomnom for the npm package name

from ied.

I belive @matthewmueller is willing to donate nom: #29 (comment)

from ied.

nom is actually quite nice and fun 👍

from ied.

Perfect! So everyone cool with nom?

I want to change the name before christmas if possible, but we need to be careful I think.

A changed name might attract new users (e.g. babel's name change was quite a big thing), those users will judge us based on the functionality we have. At the same time it might confuse those who have already heard of this project and know it as "ied".

Therefore I want to have some additional features in there before we do this and maybe some visual magic (e.g. a real website etc.). Those features include:

1. Private scoped packages (public ones are already supported)
2. Support for arbitrary tarballs
3. Support for git dependencies
   (4. Publishing)
   (5. Windows support)

I was quite busy last week, so I didn't get to a lot of the stuff I wanted to. This week I want to at least finish off 1. and 3.

Shoutout to @FarhadG also! He offered to design a logo!

from ied.

@matthewmueller Awesome thanks! I will give you a heads-up before I do.

from ied.

Yay!

from ied.

👍

from ied.

👍 for nom, beautiful name! Also, very gracious of @matthewmueller to donate – should be honored with a mentioned somewhere for sure if you go for it.

from ied.

nom logo can be an ouroboros!

from ied.

I'm all for nom. I type this 2-3 times a day by mistake anyway, I'm sure I can get used to doing it on purpose.

from ied.

@alexanderGugel stated that a project rename isn't planned anytime soon; might be worth closing this issue.

from ied.

Just mentioned on #78 the name nom. So I guess this is a plus one for this!

from ied.

wmd would also be an alternative...
(https://twitter.com/nzgb/status/691721607161761794)

from ied.

http://isithackday.com/html5-rimshot/

Try the veal... In all seriousness. Happy to rebase that PR I made if you're reconsidering a name change, just let me know what you decide. I'm partial to nom, mostly because cookie monster.

from ied.

As a daily Vim user, I vote for nom because of its proximity to hjkl.

from ied.

If you need justification try this: https://gist.github.com/Hypercubed/ed622868551761dc9ede

from ied.

I own the ung package name. Do you like it?

But nom is an awesome choice as well.

Can we maybe figure out how to merge ied and pnpm and rename the project after the merge happened?

from ied.

Using nom might be a problem because there is a popular project called noms

from ied.

ipm (impressive package manager)

from ied.