ied is looking for a better name!

[jdrydn]

http://lmgtfy.com/?q=ied&l=1

[m90]

Same here.

[bcherny]

ya, pretty loaded name :|

[jdrydn]

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?

[alexanderGugel]

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.

[bcherny]

• 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")

[jdrydn]

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

• 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?

[benatkin]

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

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

[dthree]

pmn isn't taken. (Package Man)

[es128]

jpi - Javascript package installer

not taken

[alexanderGugel]

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

[es128]

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.

[jdrydn]

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

[MylesBorins]

mopp (manage our packages please)

[zeke]

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

:point_up:

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

[eisisig]

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

Oh didn't read all the thread :-/

[dthree]

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

[benatkin]

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

[zeke]

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.

[matthewmueller]

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 :smile:

[namlook]

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

[alexanderGugel]

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.

[dthree]

Gotcha on the similarIty between the two.

The anagram kind of was intentional :smile:

[rauchg]

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

$ x install

rolls off the keyboard really nicely

[alexanderGugel]

:+1: for XPM

I was also thinking about ESB and OPF.

[dthree]

:+1: on xpm. Stands out.

[FarhadG]

I like XPM. Legit. :+1:

[alexanderGugel]

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

[FarhadG]

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

lpm is easy to type

[alexanderGugel]

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?

[FarhadG]

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