Re: Blog post for review

On Wednesday, June 12, 2013 at 12:30 AM, Andrea Giammarchi wrote:

> Marcos I've created (tried to) a working video recorder and decoder with Animated GIF fallback and the only browser that worked was actually Opera 'cause all material out there, in terms of demo/examples, is outdated accordingly with specs.
>  
> https://github.com/WebReflection/wine#readme
How is this a prollyfill? It seems like an app proper.   
>  
> Talking abut getUserMedia and video ... things are different, as explained in the related blog:
> http://webreflection.blogspot.com/2013/02/the-difficult-road-to-vine-via-web.html\

So, the problem you are having here is that Browser vendors keep putting unfinished APIs on the open Web too early without using about:flags. They should stop doing that as it's clearly harmful to the ecosystem. But, on the other hand, there needs to be more possibility to enable experimental APIs easily for demos, etc. to get people excited about a feature and to get people working with them to find the issues with an API… it's a tough problem.  
> I always think out of the box but sometimes that ain't useful ... I need support and better/faster delivery from both W3C and Browsers

Again, that's a tough one. We all want things yesterday, but that's not feasible without some kind of solution/process. Making prollyfills of APIs can help speed things up a bit as it allows people to find issues with an API faster (because you actually have to read the spec and implement what it says - this speaks to the issues that François tried to discuss in his post by did't explicitly mention it: people writing specs rarely prototype their APIs in JavaScript before it's too late and they get implemented in browsers with C++ … by which point it's often too late to change stuff - case in point, the DAP Proximity APIs). Prollyfills also tend to generate tests, which is helpful for the standardization process… and prollyfills that become successful and are actually used on the Web help expose real user problems (beyond use cases) that can feedback into a Working Group with the help of developers.    
  
--  
Marcos Caceres

Received on Wednesday, 12 June 2013 15:23:32 UTC