A manifesto/draft

All,

Over the weekend there was an interesting conversation on the web
components list in which some folks are really trying to keep things
prollyfillable and others who are worried that this sacrifices the api we
really should have.  I have (mostly) straight in my own head how i think
this optimally should work and our own list has had numerous discussions on
it in terms of describing our own work and what it means.  I was thinking
about blogging about it, but then i thought: we have never really codified
a "manifesto" or proposed lifecycle/philosophy anywhere but on the list and
in blogs.  Now that this idea is growing perhaps we should.  Do you think
it is worth creating a "speculative pollyfill (prollyfill)" manifesto or
draft?

Received on Monday, 15 April 2013 13:07:16 UTC