W3C home > Mailing lists > Public > public-nextweb@w3.org > July 2013

Re: When does a library become a prollyfill?, was Re: Deliverables Re: TPAC

From: Marcos Caceres <w3c@marcosc.com>
Date: Tue, 30 Jul 2013 16:52:48 +0100
To: Brian Kardell <bkardell@gmail.com>
Cc: Yehuda Katz <wycats@gmail.com>, public-nextweb@w3.org
Message-ID: <4C33177A7AC04726A210D865D2F1A2F0@marcosc.com>

On Tuesday, July 30, 2013 at 1:30 PM, Brian Kardell wrote:

> I suppose, but many libraries aren't even trying to provide a proposal or an implementation of a proposal. Many are whole frameworks with stacks of dependent assumptions. More often, I think, libraries are fueling ideas for proposals by creating new useful abstractions. Eventually, more targeted ideas fall out. RSVP provided an implementation of a targeted promises proposal. Each selector plugin in hitch provides a targeted implementation of a proposal. I think there is a community process to be had which lets ideas pass hurdles so that these sorts of things are more obvious with feedback... In fact, that's more what I am looking for with something like this.

That makes sense. I guess maybe this means watching the landscape to see what things people are taking up in the wild - would be cool to ask library/framework creators to talk to us and let us know interesting things they have come up with to solve particular problems. The next 100 "promises" could already be out there being used and we are not seeing it … forest from trees and all that jazz.   
Marcos Caceres
Received on Tuesday, 30 July 2013 15:53:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:05:54 UTC