DZone
Web Dev Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Web Dev Zone > The First ECMAScript.next Features in Firefox and Chrome

The First ECMAScript.next Features in Firefox and Chrome

Axel Rauschmayer user avatar by
Axel Rauschmayer
·
Jan. 18, 12 · Web Dev Zone · Interview
Like (0)
Save
Tweet
8.34K Views

Join the DZone community and get the full member experience.

Join For Free
The next version of ECMAScript (code-named ECMAScript.next [1]) will be standardized by 2013. This post enumerates the first features that are currently being tested in Firefox and Chrome.

Firefox

Dave Mandelin mentions Mozilla’s ES6 planning page. He points out the following highlights (paraphrasing an email of his):

  • Mostly done: weak maps, simple maps and sets
  • The old proxy spec has mostly been implemented, but not the newer direct proxy spec
  • for...of is partially finished
  • The implementation of modules is starting

The block-scoped let and const have been available in Firefox for a long time.

V8 (Chrome, Node.js)


A post on Google+ provides details on V8. Quoting François Beaufort:

A new flag named Enable Experimental JavaScript appeared in the chrome://flags page of the last Chromium build. This flag enables web pages to use experimental JavaScript features.

A code search suggested by Paul Irish shows the relevant flags:

DEFINE_bool(harmony_typeof, false, "enable harmony semantics for typeof")
DEFINE_bool(harmony_scoping, false, "enable harmony block scoping")
DEFINE_bool(harmony_proxies, false, "enable harmony proxies")
DEFINE_bool(harmony_collections, false,
            "enable harmony collections (sets, maps, and weak maps)")

Andreas Rossberg elaborates:

... the --harmony flag currently activates the following experimental features for V8:
  • block scoping, let, const, block functions
  • [old] proxies, though not direct proxies yet
  • maps and sets
  • weak maps
  • typeof null reform
On the browser side, that should become functional in Chrome 17 (some of it is in 16 already, but incomplete/buggy) by setting
    --js-flags="--harmony"
If you are on the Chrome dev channel, you should also see it show up on chrome://flags soon.


Related reading

  1. A brief history of ECMAScript versions (including Harmony and ES.next)
  2. ECMAScript.next: the “TXJS” update by Eich
  3. es6-shim – ECMAScript 6 functionality on ECMAScript 5

 

Source: http://www.2ality.com/2012/01/esnext-features.html

ECMAScript Blocks POST (HTTP) JavaScript Harmony (operating system) Chromium (web browser) DAvE (Infineon) Google (verb)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • NextJS Vs React: Key Differences, Advantages and Limitations
  • Top ALM Tools and Solutions Providers
  • Correlation Between Fast TTM and Containers
  • Saving Memory In Java: Making The Smallest Memory Footprint

Comments

Web Dev Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo