I agree, async/await is very nice. Though it is worth pointing out async/await is quite literally syntactic sugar on top of promises. Essentially adding language syntax for common promise idioms.
Like other web standards, these things tend to get implemented in a piecemeal fashion according to consensus and demand. By the time the standards are published, much of their content is already implemented in modern browsers.
For example, the ES6 spec was just published a few months ago, so it will still be a year before we see ES7. In spite of that, the async / await capabilities are sufficiently compelling and agreed upon that patches are already being reviewed for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1185106
Kangax's tables, linked in another reply, are a great way to check what the support situation is like across browsers.
[+] [-] iyn|10 years ago|reply
The best part: you can use it today with babel (I'm using it in browser and on node thanks to the power of webpack, babel and hot reloading).
[+] [-] iamstef|10 years ago|reply
[+] [-] AgentME|10 years ago|reply
[+] [-] finalight|10 years ago|reply
because I couldn't find any information on that
[+] [-] curun1r|10 years ago|reply
[+] [-] callahad|10 years ago|reply
For example, the ES6 spec was just published a few months ago, so it will still be a year before we see ES7. In spite of that, the async / await capabilities are sufficiently compelling and agreed upon that patches are already being reviewed for Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1185106
Kangax's tables, linked in another reply, are a great way to check what the support situation is like across browsers.