News for hackers. Stuff that matters.
Re:The node.js aesthetic by substack on Wednesday November 30, 2011 @10:20AM (#3295281)
> But still, having dealt with library version issues sometimes, I think "concurrent library versioning" and "sophisticated package management" sound awfully nightmarishly black-magic to me. I guess I would be more on the "let's understand the most of what happens and not change what don't need to" kind.

Concurrent versioning lets you do the "not change what don't need to" part really, really, well. Versions of packages that have been proven to work well with one another can continue to do so because if you need a newer version of some library then both the old and the new version can live harmoniously in the same codebase. You don't need to be paranoid about upgrading modules anymore because node and npm are already paranoid on your behalf.

Re:The node.js aesthetic by moe on Wednesday November 30, 2011 @12:46PM (#3295917)
because node and npm are already paranoid on your behalf.

Yes, until npm blows up in obscure ways. Which it likes to do frequently.

Re:The node.js aesthetic by IsaacSchlueter on Wednesday November 30, 2011 @02:18PM (#3296410)
What do you mean by "blow up in obscure ways"?

It generally dumps a ton of colorful errors to your terminal. If you find them obscure, please be comforted by the fact that I certainly do not find them obscure, and would love to fix whatever problem they indicate. It's actually my job.

Also, npm is a software program, and not intelligent. It doesn't "like" things. To the extent that it has preferences, it loves semantic versions, accurate metadata, and especially you.

Re:The node.js aesthetic by IsaacSchlueter on Thursday December 01, 2011 @10:17PM (#3302519)
Moe,

So, when you say "obscure blowup", do you mean, "someone posted any issue whatsoever"?

Several of those are feature requests, or node-core bugs, or things that have been fixed.

I find your blowup very obscure. As for npm failing for you, gist or it didn't happen.

Re:The node.js aesthetic by moe on Friday December 02, 2011 @07:36PM (#3306429)
So, when you say "obscure blowup", do you mean, "someone posted any issue whatsoever"?

No, I mean "random malfunction without clear indication of what happened and how to fix it".

Several of those are feature requests, or node-core bugs

Might be a mindset thing. How many of the 8 bugs qualify as feature requests/node bugs for you?

gist or it didn't happen.

The gist is that npm needs to become more defensive, clearly state its own dependencies, and not barf random stack traces in the face of problems. You should also have a unix-guy fix the installer. Demanding 'sudo' is not only an embarrassing but also a potentially dangerous mistake.