Over the years there has been an increase in the popularity of promises in Node.js and JavaScript in general. This popularity is evidenced by the Promise object becoming part of the ECMAScript specification. As a result of having promises built-in, the language can add new capabilities that rely on them. Async functions are a prime example of a new language feature that uses promises. One reason f
I'm probably going to regret this, but this post is about promises. There are a few details that I'd like to spell out so I can point people to this post instead of repeating myself. First, let's talk about try/catch. The problem with exception handling in JavaScript is that it's too aggressive. Consider the following code: try { var result = foo(getValue()); } catch(e) { // handle error from `foo
#error_handling_sushi でJavaScriptのエラーハンドリングについて議論した。 自分はPromiseのエラーハンドリングの握りつぶしの問題を見つけやすくするイベントの実装について、Promise Error Handlingという話をした。 ログ: #error_handling_sushi - Togetterまとめ #error_handling_sushi 始まった #寿司とは pic.twitter.com/XZe21QTsDO — Takuto Wada (@t_wada) March 6, 2015 – 基調講演 - teppeis これが #error_handling_sushi pic.twitter.com/vSLDpthYi4 — azu (@azu_re) March 6, 2015 #error_handling_sushi 基調講演 一
I spent a few days looking at the latest specs of ES6 Promise [1], which is based on Promise/A+ [2], that is available on the latest Node v0.11. To be honest I quite like the design patterns provided by promise and how they work well with generators. However I also think that the current specification only partially solves the problem of asynchronous control flow. In fact I think there are some s
The official Change.org Product Development blog, writing about product, design, and engineering at the world's largest petition platform. We’ve standardized on using promises to manage most of the asynchronous interactions in our JavaScript codebase. In addition to really enjoying the extra expressiveness and aggregation possibilities offered by promises, we’re benefitting greatly from richer err
As we saw in Part 1, error handling in callback-based asynchronous code gets messy quickly, and loses many of the qualities of synchronous code that make it familiar and easier to reason about. In Part 2, we introduced Promises and saw how they restore call-and-return semantics, allow errors to propagate up the stack similarly to synchronous exceptions, and generally provide a cleaner approach to
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
