Live data from Hacker News

Node v0.10.14 (Stable)

blog.nodejs.org

21–30 of 33 posts

Re: Node v0.10.14 (Stable)

#22
post #18

Earlier quoted context omitted.

You mean besides the binaries on the page linked in this post? I've also been using a PPA to keep an up-to-date version on my home Ubuntu box for playing around with.

Oh, so am I supposed to drop the binaries to my bin or sbin directory? Which PPA did you use?

The main download area has a link to "Installing from Package Managers"[0] which links to "Installing Node.js via package manager" [1]. This page has information on setting up the PPA for Ubuntu/Mint.

[0] http://nodejs.org/download/

[1] https://github.com/joyent/node/wiki/Installing-Node.js-via-p...

Re: Node v0.10.14 (Stable)

#23
post #16

For anyone willing to learn node which would be an easy way to install the latest version on a server? Ubuntu 13.04 repository only has node v0.6.19

Just use nvm[1]. It's awesome, use it dev/prod. It's also easy to build and install from source on debian-based distros (my only experience).

[1] https://github.com/creationix/nvm

Re: Node v0.10.14 (Stable)

#24
post #6
post #5

Earlier quoted context omitted.

I guess it wasn't so stable after all.

Stable mean feature complete. Not bug free.

To me it also means "stable API", which means published APIs are neither removed nor their function signatures changed (cough Ruby).

Re: Node v0.10.14 (Stable)

#25
post #11
post #3

I've recently gotten into Node and it has been such an awesome and fun time. Anyone on the fence about it should definitely go and try it out.

To chime in with another viewpoint: I've just written a sort of remote-control solution that can use WebSockets and fall back to SSE (Server-Sent Events) + HTTP POST if necessary. I wrote it in node.js, which I hadn't used before, because it had (has) great libraries for both WebSockets and Server-Sent Events. So I though I would put to use the adagio "best tool for the job". I don't regret it because I was able to w…

Promises are the only real solution. https://github.com/kriskowal/q

Re: Node v0.10.14 (Stable)

#27
post #25
post #11

Earlier quoted context omitted.

To chime in with another viewpoint: I've just written a sort of remote-control solution that can use WebSockets and fall back to SSE (Server-Sent Events) + HTTP POST if necessary. I wrote it in node.js, which I hadn't used before, because it had (has) great libraries for both WebSockets and Server-Sent Events. So I though I would put to use the adagio "best tool for the job". I don't regret it because I was able to w…

Promises are the only real solution. https://github.com/kriskowal/q

It's still callback spaghetti though right.

You still need to break function "doAll()" into function "doPart1()", "doPart2()"...,"doPartN()". It's just that now you have a new syntax for calling all of the functions. Like Rx for JavaScript instead of C#.

I do believe the syntax for calling all of the component functions is better.. but it would be great if you didn't have to make the component functions at all.

Re: Node v0.10.14 (Stable)

#28
post #3

I've recently gotten into Node and it has been such an awesome and fun time. Anyone on the fence about it should definitely go and try it out.

+1 Node is lots of fun, and a good platform for JavaScript. As a long time (since the late 1970s) Lisp programmer (also with lots of Ruby and Java work) I have in the past generally detested JavaScript. That has changed, big time. I now find that JavaScript (and CoffeScript) is really a nice language. By using a small subset of the language, and always having JSLint running in IntelliJ: coding is fast, code is readab…

I would love to hear a more detailed reason why. I'm in the opposite boat. Been using node on a number of projects, have recently discovered clojure and want to get away from node and to clojure, once I can justify doing so.

Logging, toolchain, ease of deployment, and callback hell on "large" projects are the reasons that I'm down on node.

-edit- basically help me understand the skeletons in the closet you've discovered in clojure -edit-

Re: Node v0.10.14 (Stable)

#30

Earlier quoted context omitted.

+1 Node is lots of fun, and a good platform for JavaScript. As a long time (since the late 1970s) Lisp programmer (also with lots of Ruby and Java work) I have in the past generally detested JavaScript. That has changed, big time. I now find that JavaScript (and CoffeScript) is really a nice language. By using a small subset of the language, and always having JSLint running in IntelliJ: coding is fast, code is readab…

I would love to hear a more detailed reason why. I'm in the opposite boat. Been using node on a number of projects, have recently discovered clojure and want to get away from node and to clojure, once I can justify doing so. Logging, toolchain, ease of deployment, and callback hell on "large" projects are the reasons that I'm down on node. -edit- basically help me understand the skeletons in the closet you've discove…

There are no skeletons in the Clojure world: beautiful language and solid infrastructure. My point is that JavaScript, Node, Meteor, etc. seem a bit more practical for some things I have been working on.
Post reply on HN