What's new in 3.3?

- Brush transitions http://bl.ocks.org/mbostock/6216724

- Tools to help dynamic simplification (scale appropriate geometry on zoom): http://bl.ocks.org/mbostock/6252418

- Bug fixes

- Others?

In terms of rendering speed, how efficient is CSS compared to webGL or other related 3D technologies?

I found Async Javsacript by Trevor Burnham super helpful for learning how use promises properly. However, it doesn't cover the javascript implementation of a promise (uses jQuery), so this is a nice blog post complementing that material.

jQuery loosely follows the Promises/A spec [1], so Q.js [2] might have been better choice.

[1] http://domenic.me/2012/10/14/youre-missing-the-point-of-prom... [2] http://documentup.com/kriskowal/q/#

I disagree. I would rather see examples of Promises in pure Javascript. It is the more general approach and not everyone uses jQuery.

My mistake. I thought the blog post was about using jQuery. I totally agree with you.

since jquery 1.8 they fixed the most outrageous limitation with their deferred implementation (then should return a new promise), and I actually prefer their implementation.

that said, i make use of underscore.deferred, which is the jquery implementation as an underscore mixin.

I wonder if there's a more general issue with public video services getting abused by adult content. Interesting to see how (if?) Google deals with this problem...

How is it abuse exactly? Live consenting naked people in exchange for money is not illegal in much of the world.

Guess if you try to get help fixing your bike and get a big penis :)

It's possible that by vetting the initial users they can create a community that would self police any abuse.

Technically speaking, HTML 5 introduced web-workers which allows javascript to have multiple threads (see 1). However, it's still useful to think about them as being single threaded since workers are sandboxed, meaning they don't have access to the global namespace. This avoids issues commonly found in concurrent programming. E.g., separate threads cannot read and write to the same variable since they don't have access to each other's namespaces.

[1] https://developer.mozilla.org/en-US/docs/Web/Guide/Performan...

While that's true, I don't believe it's applicable to node.js, so it's a bit out of scope for this article.

People coming from multi-threaded server environments should be aware that multi-threading does in fact exist in Node (scope of parent comment), but it's rather different from other more common concurrent event handling schemes. I.e., you cannot have shared mutable variables across threads (scope of article and ongoing async discussion). For examples, see https://npmjs.org/package/webworker-threads and https://github.com/cramforce/node-worker.

Fascinating. I didn't know that webworkers were available in node.js. I stand corrected, then.