- From: Marcos Caceres <w3c@marcosc.com>
- Date: Tue, 18 Dec 2012 17:08:01 +0000
- To: Clint Hill <clint.hill@gmail.com>
- Cc: François REMY <francois.remy.dev@outlook.com>, Brian Kardell <bkardell@gmail.com>, public-nextweb@w3.org
On Tuesday, November 27, 2012 at 3:32 PM, Clint Hill wrote: > I think François coalesced the question for me: In what ways are polyfills similar to prollyfills codewise? > > I can make assumptions that they both have: > > - Syntax extensions/changes to HTML/CSS/JavaScript Agreed. > - Parsers to read/detect said extensions/changes to the syntax Potentially. > - Scripts to add behavior/state to said extensions/changes Very likely. > > The one significant difference between polyfills and prollyfills is that polyfills add 1 step there for feature detection or lack thereof. I think you do this regardless in a prollyfill. You don't want to prollyfill if you don't have to. > > Having said all that, are we interested in determining the "state of the art" in those similarities or are we interested in determining that difference? > > I would want to read up on polyfills (and frankly I've read a number of them in order to add them to a framework I was once involved with … bleh ...) if the goal is to find "state of the art" for the similar things. But if the goal is to try and figure out the 1 difference, I think I'm confused. I think we should just try to figure out some of the best ways of defining and coding them. > > Sorry if I'm making much to do about nothing. But I have to agree with Brian, my skin becomes itchy when I see the word polyfill in our conversations. Fair enough. -- Marcos Caceres
Received on Tuesday, 18 December 2012 17:08:31 UTC