Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Habits of a Happy Node Hacker

blog.heroku.com

Post reply on HN
Print view View original

11–20 of 56 posts

Re: Habits of a Happy Node Hacker

#11

Post by userbinator »

sonnyp wrote: post #5
bshimmin wrote: post #3

Node.js is the rare example of a Linux-centric tool with great cross-platform support. Apart from the problems with Windows, npm, and path lengths.

It was an npm issue, fixed in npm 3. http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really...

I may be somewhat biased because my primary platform is Windows, but IMHO 260 bytes is plenty for a full path. I've personally never run into that limit with what I do, but I'm aware that there are some programming languages and environments which even encourage very deep nesting (often with directories that contain nothing more than another one), making it much harder to navigate the resulting structure. It's good to see the Node.js people recognise this situation and go back to flatter hierarchies, even if it was Windows' path length limitations that motivated it.

http://blog.codinghorror.com/filesystem-paths-how-long-is-to...

Re: Habits of a Happy Node Hacker

#12

Post by [deleted] »

userbinator wrote: post #11
sonnyp wrote: post #5

Earlier quoted context omitted.

It was an npm issue, fixed in npm 3. http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really...

I may be somewhat biased because my primary platform is Windows, but IMHO 260 bytes is plenty for a full path. I've personally never run into that limit with what I do, but I'm aware that there are some programming languages and environments which even encourage very deep nesting (often with directories that contain nothing more than another one), making it much harder to navigate the resulting structure. It's good t…

[deleted]

Re: Habits of a Happy Node Hacker

#13

Post by cvburgess »

The article suggests using node-foreman (#6); can someone explain the advantage of Procfile-based environment management? I read the docs and didn't see anything that couldn't be handled by a simple config.json or some environment variables.

Re: Habits of a Happy Node Hacker

#14

Post by netcraft »

userbinator wrote: post #11
sonnyp wrote: post #5

Earlier quoted context omitted.

It was an npm issue, fixed in npm 3. http://www.felixrieseberg.com/npm-v3-is-out-and-its-a-really...

I may be somewhat biased because my primary platform is Windows, but IMHO 260 bytes is plenty for a full path. I've personally never run into that limit with what I do, but I'm aware that there are some programming languages and environments which even encourage very deep nesting (often with directories that contain nothing more than another one), making it much harder to navigate the resulting structure. It's good t…

The new babel 6 stuff was the first time I had hit the limitation, but their names are extraordinarily long.

Re: Habits of a Happy Node Hacker

#15

Post by vog »

secretagent wrote: post #2

Regarding point 9, if you don't check your `node_modules` into version control don't you run the risk of them disappearing from NPM?

Even when assuming availability, what about modules that change?

Either because authors "bugix" their existing versions and don't bother to increase the version number. Or because a malicious network actor delivered modified code.

That's why I prefer to add a SHA-256 hash/checksum to every downloaded dependency file. In some settings that hash might be more important than the actual version number.

Re: Habits of a Happy Node Hacker

#16

Post by jtwebman »

bshimmin wrote: post #3

Node.js is the rare example of a Linux-centric tool with great cross-platform support. Apart from the problems with Windows, npm, and path lengths.

Path lengths is a windows issue not a node one. The same issue exists for C# or any windows language. BTW this is fixed with the latest npm!

Re: Habits of a Happy Node Hacker

#17

Post by schwuk »

cvburgess wrote: post #13

The article suggests using node-foreman (#6); can someone explain the advantage of Procfile-based environment management? I read the docs and didn't see anything that couldn't be handled by a simple config.json or some environment variables.

The article is on heroku.com, so of course it's going to encourage Heroku-centric solutions.

Re: Habits of a Happy Node Hacker

#19

Post by acbabis »

#4 seems spurious. Just another example of "If everyone did it my way, then everyone would be doing it my way." What if people don't want to do it your way? What if people can actually remember to spell correctly? EDIT: *nix has case-sensitivity so that people can actually use it.
Post reply on HN