New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm does not stand for "node package manager" #34
Conversation
It is also not capitalized :-)
To be more accurate, npm isn’t “the package manager for Node.js”, but “a package manager for JavaScript”. There is nothing tying it to Node.js, and it can be (and is) used in other contexts (which they prominently show on the top of the website). Node.js uses npm by default as a package manager, but other than that they don’t have a much deeper link. |
Read the first readme for npm and I think you'll agree they are quite deeply linked. Even if the projects have diverged, "node package manager" is totally accurate, if not up to date. |
You seem to be arguing a definition is valid today because it was valid in the past. That makes no sense.
npm is the package manager Node.js uses, it is not Node.js’s package manager; it does not serve them. That wording and definition is limiting, and implies npm is useful because of and perhaps even dependent on Node.js, which is false. Even if it were true in the past, it is irrelevant now, and for the article. If at one point in time ed billed itself as the best way to edit text and it was true1, that no longer holds true today simply due to those past claims. I’ll say it again: if the projects took different routes they are different things, and their history bears no relevance to this particular sentence. npm is, as of today, not simply Node.js’s package manager, which makes this sentence, written in the present tense, inaccurate. Their README of the past is without a doubt less relevant and important for the present than the top of their current homepage and their current README. 1 Not saying it did or it was, merely making a point. |
It's actually not a package manager at all. NPM stands for Node Package Maid. |
@vitorgalvao: it is both the package manager for node.js and a package manager for JavaScript (I wrote the copy for the website, but feel like "the" package manager for JavaScript is perhaps getting ahead of reality a little bit). Either way, in this context I thought the former was more relevant :-) |
Which is why I called it, in the first reply, a package manager for JavaScript. I also started by saying “to be more accurate”. I do not think your current definition is wrong, just that it should be broader and more complete by not limiting the definition to Node.js. |
In the context, the point of the sentence is not to fully define the scope of npm and its exact definition. It's to introduce npm and explain why it's relevant to the non-technical person reading the article. Somebody who is only just finding out that Node.js exists is not going to want to learn about io.js etc. etc. |
Which both definitions do, with the exact same amount of words, with none of them being simpler to understand than the other. Given that, there is absolutely no reason to not use the more correct, broader definition. It’s not like we’re talking about explaining the whole backstory, here, both definitions are correct and simple, but one of them is more accurate. |
Okay. How about "as the CTO of npm, Inc., I think it's less confusing if our product was described in this context as the package manager for node.js rather than introducing its (more accurate, but not relevant) role as a package manager for javascript"? |
Your position is irrelevant to the matter, and gives you no special powers.
Expressing your opinion, though, is perfectly valid.
It’s there we disagree. You spoke about non-technical people before. Most people I know are non-technical; some know what JavaScript is, none has any clue what Node.js is. It is clear we won’t reach an agreement, though. We both made our points, so whoever is in charge of making the change has enough information to make an informed decision. |
OH BUT WAIT THE PLOT THICKENS npm/npm@226a677#diff-0743750f368afcb1060491fc9755e3d8 |
This thread is getting better and better. :) |
One idea: We could wait until mid or late 2016 to let things settle down, then decide on the best course of action. |
I am deeply sorry I got involved in the first place. There's your metaphor for open-source participation, Paul. |
... mumble, mumble... ECMAScript... mumble... should be epm by rights... mumble... |
"Node package manager" is just one of many ridiculous and non-sensical made-up expansions of npm. What would that even mean??? |
@disusered I'm operating on the assumption they are ribbing each other. Joking aside I think @seldo's change is correct for the target audience. While it may be used for other things, npm is first and foremost, a package manager for Node.js |
It was simpler when we were arguing about the name of the Pathologically Eclectic Rubbish Lister. |
After we sort this out we can set everyone straight on how to pronounce "OS X." |
say "OS X" |
utter "OS X" |
epic thread is epic 💯 🎱 OS X is pronounced "Auss Ex". |
OS X has OS silent. |
While |
\o/ |
It is also not capitalized :-)
I loved this article. An epic poem for the internet age.