[coldtea]

>Much faster if you are willing to punish your users for using subpar browsers that don't keep up with current technologies and standards.

Actually Chrome is a complete mess ES6 compatibility wise.

Most of the interesting stuff is unimplemented still, and what is there is hidden in options the user has to specifically enable.

Sure, the standard is (now) only due for 2015, but Chrome dragging its feet is also one of the reasons for that. And it's not like FF waited for the standard to be stamped and released to have the implementations according to the standard already working.