5 ms·

You're being voted down because they are not actually that outrageous. "purity of non-blocking libraries": the context makes it explicitly clear he is not talk

by sjs 15y ago

You're being voted down because they are not actually that outrageous. "purity of non-blocking libraries": the context makes it explicitly clear he is not talking about side effects and referential transparency. If I were more mean spirited I might say that you don't understand how to parse a sentence or that words can take on different meanings in different contexts. I'm certain that's not actually true but that is effectively the conclusion you came to in the same situation. Pretty silly right? If you followed the Node mailing lists you'd see that there are questions about allocating gigabytes of memory with Node, and Ryan has to shrug and say "Sorry, Node isn't for you because v8's memory management doesn't facilitate such use". Also he mentions that he likes to win benchmarks and the GC gets in the way of that. Whether or not winning benchmarks is useful is debatable, but given that constraint it's obvious you don't want GC. He wants a scripting language without GC not JavaScript specifically. Give the guy some credit, he is a C programmer by trade. Didn't read the stuff about Akka and can't comment on that but after the first 2 criticisms I'm not going to waste my time.

KirinDave 15y ago
> If I were more mean spirited I might say that you don't understand how to parse a sentence or that words can take on different meanings in different contexts. I'm certain that's not actually true but that is effectively the conclusion you came to in the same situation. Pretty silly right? Ahh so let's just play word games then? Let's just call callbacks "allocators of effect" and functions "parameterized callbacks" and see how clear our writing is. Even if we ignore this gaffe, it implies Ryah thinks the world is struggling under the burden of blocking libraries. "Oh no," our hypothetical wage slave might cry, "this library unexpected uses a thread. Now my job is impossible." It's strange to even claim that a feature in 2011. Maybe Node's needs a Paul-Tyma-figure to come snap them out of their implicit assumption that asynchronous libraries are always faster; they are not. But what he said wasn't true. You can write loops in Javascript, so libraries could enter into infinite loops which would stop the machine from progressing. > Whether or not winning benchmarks is useful is debatable, but given that constraint it's obvious you don't want GC. He wants a scripting language without GC not JavaScript specifically. He was not asking or direct allocators and deallocators, if you read the quote, he was talking about removing memory management entirely. I'm not sure how Node's functions could lexically close over anything unless you start introducing a lot of new notions that current node programmers don't care abut. > Give the guy some credit, he is a C programmer by trade. I want to. I really want to. But then he writes blog posts like this (http://antirobotrobot.tumblr.com/post/5109182039/overlapped-i-o http://antirobotrobot.tumblr.com/post/5109182039/overlapped-...) and severely undermines my confidence in him. When he was just playing around with a side project I thought it was a cool hack. Now that he's got a corporate backer it's a little surprising he isn't bothering to up his game.
- deleted 15y ago
  [deleted]

by sjs 15y ago

KirinDave 15y ago

> If I were more mean spirited I might say that you don't understand how to parse a sentence or that words can take on different meanings in different contexts. I'm certain that's not actually true but that is effectively the conclusion you came to in the same situation. Pretty silly right? Ahh so let's just play word games then? Let's just call callbacks "allocators of effect" and functions "parameterized callbacks" and see how clear our writing is. Even if we ignore this gaffe, it implies Ryah thinks the world is struggling under the burden of blocking libraries. "Oh no," our hypothetical wage slave might cry, "this library unexpected uses a thread. Now my job is impossible." It's strange to even claim that a feature in 2011. Maybe Node's needs a Paul-Tyma-figure to come snap them out of their implicit assumption that asynchronous libraries are always faster; they are not. But what he said wasn't true. You can write loops in Javascript, so libraries could enter into infinite loops which would stop the machine from progressing. > Whether or not winning benchmarks is useful is debatable, but given that constraint it's obvious you don't want GC. He wants a scripting language without GC not JavaScript specifically. He was not asking or direct allocators and deallocators, if you read the quote, he was talking about removing memory management entirely. I'm not sure how Node's functions could lexically close over anything unless you start introducing a lot of new notions that current node programmers don't care abut. > Give the guy some credit, he is a C programmer by trade. I want to. I really want to. But then he writes blog posts like this (http://antirobotrobot.tumblr.com/post/5109182039/overlapped-i-o http://antirobotrobot.tumblr.com/post/5109182039/overlapped-...) and severely undermines my confidence in him. When he was just playing around with a side project I thought it was a cool hack. Now that he's got a corporate backer it's a little surprising he isn't bothering to up his game.

deleted 15y ago
[deleted]