Now with Safari Technical Preview, if you want access to all of it in a more accessible package than the WebKit Nightlies, you can have it.
BTW, Apple has been doing what appears to be a amazingly good work on JavaScript Core lately, extending their performance lead: https://webkit.org/blog/5852/introducing-the-b3-jit-compiler....
You might actually have a leg to stand on when Safari 9.1, released 10 days ago, gets its ES6 state tested and uploaded to the compatibility table. Or it might be more embarrassment about Apple's slow release cycle. It's also unclear as to whether Safari Tech Preview will contain the majority of ES6 code in Webkit or if it will be "curated" into a significantly less compliant and useful state. Once again, tests will tell. What is certain for now is that six months of Safari have left it at 53%, which, among many other examples, has been Safari dragging everyone else down.
Just because they have untested, unsupported code in a development branch doesn't mean that their main browser with a completely different name and a glacial release cycle gets a pass for holding up the class. The Tech Preview is a good starting step, but until these things have a clear release cycle that shows current WebKit ES6 feature support making its way into a release build before the end of the year, we'll continue to be upset at them with cause.
Apple has been clear from the moment they released Safari Technology Preview: Get a preview of the latest advances in Safari web technologies, including HTML, JavaScript, and CSS. Safari Technology Preview includes the most recent version of WebKit, the rendering engine that powers Safari.
This is from https://developer.apple.com/safari/technology-preview/
Short answer: Safari Technology Preview also scores 98% on the ES6 test.
The phrase "most recent version" could mean pulling from a dev branch, using the last successful build, pulling from a release branch, pulling from a testing branch, assigning arbitrary numbers and tags to commits and pulling from there, or even working from a staging repo where they cherrypick commits. These are all separate sources that could hve their own version series, and "most recent version" is a very relative statement. Anyone who's seen the divide between development and sales knows that phrase has enough wiggle room to fit a Challenger disaster inside, and marketing is Apple's specialty.
I really hope they start to pull the changes from WebKit. Safari sorely needs it. But Apple's not the kind of company you just take at their word unless it's independently verified. I get it if you want to believe. That's sweet. But I'd rather wait for the tests.
Even then, monthly builds are still not a public release schedule for Safari. It was six months with only minor fixes between 9.0 and 9.1. We're far more interested in a public stable release with usable ES6 support than builds with unstable features that won't be usable on sites this year. If preview builds were what would solve the problem, then the WebKit Nightlies would have been enough.
And Safari saves like 20% to 30% of your battery life over Chrome...
http://bgr.com/2015/08/05/google-chrome-vs-safari-battery-li...
http://www.theverge.com/2015/4/10/8381447/chrome-macbook-bat...
And both are due to Apple's own JIT engine...
I feel like that claim needs a source. I'd be amazed if the JS engine had anywhere near such a substantial effect on battery life.
When loading webpages, one of the most important factors to saving power is reaching an idle state as quickly as possible. For many pages, that requires being fast at executing JS that runs only once or only a few times. Safari dominates on this, thanks to WebKit and JavaScriptCore. You can see this on JSBench, which runs JS modeled on real page loads and interactions: http://plg.uwaterloo.ca/~dynjs/jsbench/
I applaud Chrome's recent work on battery life. But I think it would be fair to say that safari is still the best in this area. And also that our excellent results have inspired Chrome and others to do better, much as in an earlier era Chrome inspired other browsers to get more serious about JS performance.
Windows itself has worse battery life than OS X on identical hardware, so it's hard to compare Mac browsers to Windows browsers. Safari on OS X is the best laptop browsing power efficiency you can get, and likely the best battery life barring laptops with super huge batteries.
For example most ES2015 features have been available in Chrome, Edge and Firefox for over 6 months now, but Safari still doesn't support any of it (other than this tech preview) because it's development time is shared with the rest of Apple's ecosystem.
Unless Apple dedicates more resources to Safari in order to keep pace with the rest of the browsers, they'll be playing catch-up ad infinitum.