はてなブックマーク

This post is the beginning of a series of posts regarding some of the more interesting issues I’ve encountered while working on the Streams Standard. In the Streams Standard we have the concept of readable streams, which are an abstraction on top of the lower-level underlying sources. In an abstract sense an underlying source is “where the chunks of data come from.” The most basic underlying sourc

I want to document an interesting pattern we’ve seen emerge in some recent web platform specs, including promises and streams. I’m calling it the revealing constructor pattern. The Promises Example Let’s take the case of promises first, since that may be familiar. You can construct a new promise like so: var p = new Promise(function (resolve, reject) { // Use `resolve` to resolve `p`. // Use `reje

The W3C Technical Architecture Group has made immeasurable progress this year since the original wave of reformist thought swept through it last election season. The extensible web agenda, which I’ve spoken about previously, has been adopted into their vision for the web’s foundations and informed recent spec work across the W3C. The TAG even moved its deliverables onto GitHub, allowing better col

This post adapts my talk from JSConf EU 2013. The web platform has, historically, been somewhat of a kludge. It’s grown, organically, into something with no real sense of cohesion. Most of its APIs have been poorly designed, by C++ developers, via a binding layer meant originally for CORBA. Worse, there have been major gaps in what we can do compared to native apps. And for those things that we ca

This post originally appeared as a gist. Since then, the development of Promises/A+ has made its emphasis on the Promises/A spec seem somewhat outdated. Contrary to some mistaken statements on the internet, the problems with jQuery’s promises explained here are not fixed in recent versions; as of 2.1 beta 1 they have all the same problems outlined here, and according to one jQuery core team member

I wrote up a quick guide to the terminology around ES6’s iteration-related concepts, plus some notes and other resources. Definitions An iterator is an object with a next method that returns { done, value } tuples. An iterable is an object which has an internal method, written in the current ES6 draft specs as obj[@@iterator](), that returns an iterator. A generator is a specific type of iterator