Hard to imagine what they could be adding to CSS3 transforms - composite transforms can be done efficiently without calculating them manually anyway (by using the DOM tree as a "scene graph"). I experimented with this some time ago as well [1]

But even bigger question than the performance is, what kind of 3D user interface would be more effective in conveying a message than a clean, regular 2D website that everybody feels familiar with. Curious to see if they will bring some UI design innovations here

[1] https://github.com/asaarinen/spherical-map

Frankly the fat arrow syntax adds so little value that it's not worth adding new syntax to JavaScript, just my humble opinion.

The fat arrow seems to be primarily about easier scoping when using this - so it's trying to patch the single most broken feature a language ever had.

The existing function syntax is fine, rather just avoid using "this" at all in your code.

After the incident they are shrugging it off. My guess is that they were trying their luck; had they found anything on his laptop which they could use against him - like any of the leaked documents - who knows where he would be detained right now.

My guess is that it was like the bully who shoulder-checks you when you're walking by them in the hallway, and who just keeps on walking.

I think it's like a teacher checking your bag (under the pretence of "finding drugs") in order to confiscate your camera that contains incriminating pictures of them.

I think it's more aggressive and invasive than that. Maybe if the pictures were of the superintendent and their paramour. Maybe.

I'd guess what they were looking for was any one of the leaked top-secret NSA documents on his laptop, the hard drive of which is being analyzed as we speak...

Had they found anything during the 9 hours, I'm afraid he wouldn't be flying to Brazil - he would have been detained indefinitely as a "terror" suspect in order to intimidate Greenwald even more.

You do it like this (using async):

  async.eachSeries(
      players,
      function(player, playercb) {
	  var valid = false;
	  async.whilst(
	      function() { return !valid; },
	      function(wcb) {
  		  Ask("What's your name", function(name) {
		      if( IsValidName(name) ) {
			  player.name = name;
			  valid = true;
		      }
		      wcb();
		  });
	      },
	      playercb);
      },
      function() { /* done */ }
  );

More lines than the foreach loop, but on the other hand, if this was an operation you wanted to do in parallel instead of sequentially, that'd be impossible with the simple loop construct.

I applaud the Node developers for their effort. While recent "competitors" like Go are fascinating and in some ways even arguably better, the fact that every device on earth runs JavaScript makes me bet that Node will prevail.

Computing will need to move fluently between the cloud and the terminal, and JavaScript is the only language which allows you to use a single codebase for both (in the foreseeable future). As developer time will stay the biggest expense when developing software, I am bullish on Node and JavaScript.

I disagree with the idea that "[...] every device on earth runs JavaScript makes me bet that Node will prevail."

Because Node does not strictly equal Javascript-- V8 is not Javascript, nor is spider monkey. Most node applications, without some modification, do not run in the browser. They are missing tons of libraries and cannot interact with the file system.

I do appreciate the ability to have a single codebase, but over the past few years, I've pivoted and hope to someone's god that it is NOT javascript. Mostly because, in my experience, Javascript itself, even with a great focus from the beginning, is incredibly difficult to maintain.

Even then, is having a codebase in one language the best idea? There are some things that are much better to write in Erlang than they are C, and vice versa. It depends on the problem you're trying to solve.

The bigger the project, the less Javascript I want in it.

I think ASM.js, or something similar, will be the death of writing Javascript. Then it won't matter what language it's written in, we can use source maps to debug and it'll be faster than we could've ever written by hand*

*single one off functions don't count. Try writing a webapp in pure x-86 assembly.

These days virtually every language can be compiled to JavaScript in a very usable manner. For example, I've had a lot of success with js_of_ocaml[1], not really running into any of the problems people like to harp about regarding compiled-to-JS languages.

[1]: ocsigen.org/js_of_ocaml/

The argument for developer time--as well as decreased maintenance cost--is exactly why I went with OCaml over pure JavaScript. And so far it's certainly paid off!

Sure, but the language that _every_ developer will need to know is JavaScript, not OCaml or some other of the dozen alternatives that can be compiled to JS.

Besides, the ability to compile to JS is not enough; you will need to read it in JS, debug it in JS and let other developers work on it in JS (because they don't know OCaml).

Does _every_ C or C++ developer know the ISA they're targeting? Also, source maps.

It might actually make sense to Snowden to get some level of guarantees of good treatment and fair trial from Holder, and then take a commercial flight to US of his free will

What an arrival it would be!

If he got to decide the choice of jurisdiction (or Hawaii), civil trial with a jury, fair treatment and legal advisory, he would even have a chance of getting the jury to nullify - and worst case of 10 years (?) would not be unbearable compared to a lifetime of exile

As a side note, I don't really know how Holder can state that US does not torture with a straight face

Read: Snowden should publish everything he has, because after that he will be granted asylum.

What better way to get everything out of Snowden, still stay "neutral" and give USG the diplomatic finger

Just in case somebody's interested, here's a related experiment we made to generate and display map tiles in a "google earth-style" projection using CSS transforms:

https://github.com/asaarinen/spherical-map