Good for him, I guess, but does those springs not give him an advantage? How would you even go about measuring that?
Yes, the chunk of memory is managed by node, but each Buffer instance is linked with a slice of the heap through `v8::Object->SetIndexedPropertiesToExternalArrayData()`, the same way a JS `Uint8Array` would. Here's…
Node.js Buffers are actually built on top of V8's Uint8Array. Using 32-bit integers to represent 8-bit values seems quite wasteful.
As someone who hasn't really explored client-side MVC yet, my impression is that Backbone.js is the clear leader at this point.
I love CoffeeScript, and I would hate to see this become part of the language specification. Just a few things off the top of my head: - Why does defer() look like any other function. - Completely changing the return…
Good for him, I guess, but does those springs not give him an advantage? How would you even go about measuring that?
Yes, the chunk of memory is managed by node, but each Buffer instance is linked with a slice of the heap through `v8::Object->SetIndexedPropertiesToExternalArrayData()`, the same way a JS `Uint8Array` would. Here's…
Node.js Buffers are actually built on top of V8's Uint8Array. Using 32-bit integers to represent 8-bit values seems quite wasteful.
As someone who hasn't really explored client-side MVC yet, my impression is that Backbone.js is the clear leader at this point.
I love CoffeeScript, and I would hate to see this become part of the language specification. Just a few things off the top of my head: - Why does defer() look like any other function. - Completely changing the return…