3 ms·

> he claims a big advantage of node libraries is their "purity", but it's pretty obvious that he doesn't know what that word means He said: "purity of non-bloc

by judofyr 16y ago

> he claims a big advantage of node libraries is their "purity", but it's pretty obvious that he doesn't know what that word means He said: "purity of non-blocking libraries" which has nothing to do with purity in the functional sense of the word, but rather that there are no blocking libraries. "Pure" has several meanings and I don't see how you can mix them up with the context given here… > But javascript's object model really wouldn't allow manual memory management. Huh? Why? How can anything not allow manual memory management? > What I don't think he gets is how the scheduling for actors works. It's actually an alternative paradigm to the callback soup that Node uses. He wrote two sentences that he wanted "something Akka-like" and that he wanted to "connecting Akka actors". Very vague statements from his side; how can you claim he don't understand how it works?

KirinDave 16y ago
> He said: "purity of non-blocking libraries" which has nothing to do with purity in the functional sense of the word I'm sorry, but the word is bizarrely used here. I challenge you to find a single use of this word in this sense in the literature of our profession. I'd be surprised if you could. If he had not used that word, the sentance would have been clearer. And it's not even true. A library could contain an infinite loop, which will do what blocking does. > Huh? Why? How can anything not allow manual memory management? Languages with closures and callbacks have a pretty damn hard time with explicit memory managment. And please note that he didn't say he wanted some explicit memory management features, he said he wished Javascript didn't have garbage collection (like C). This isn't, "I sure do wish I could manage some buffers." > Very vague statements from his side; how can you claim he don't understand how it works? Because Akka's and Erlang's dispatch model is inimical to the way Node.js does business.

by judofyr 16y ago

KirinDave 16y ago

> He said: "purity of non-blocking libraries" which has nothing to do with purity in the functional sense of the word I'm sorry, but the word is bizarrely used here. I challenge you to find a single use of this word in this sense in the literature of our profession. I'd be surprised if you could. If he had not used that word, the sentance would have been clearer. And it's not even true. A library could contain an infinite loop, which will do what blocking does. > Huh? Why? How can anything not allow manual memory management? Languages with closures and callbacks have a pretty damn hard time with explicit memory managment. And please note that he didn't say he wanted some explicit memory management features, he said he wished Javascript didn't have garbage collection (like C). This isn't, "I sure do wish I could manage some buffers." > Very vague statements from his side; how can you claim he don't understand how it works? Because Akka's and Erlang's dispatch model is inimical to the way Node.js does business.