Re: IndexedDB, what were the issues? How do we stop it from happening again? from John Kemp on 2013-02-11 (www-tag@w3.org from February 2013)

From: John Kemp <john@jkemp.net>
Date: Mon, 11 Feb 2013 11:25:01 -0500
To: Marcos Caceres <w3c@marcosc.com>
CC: Kingsley Idehen <kidehen@openlinksw.com>, www-tag@w3.org
Message-ID: <51191B5D.7040102@jkemp.net>

On 02/11/2013 11:11 AM, Marcos Caceres wrote:
> If you are accustomed to
> working with complicated APIs (e.g., you come from Java or
> something), then you might just be wondering what all the whinging is
> about… but if you come from, say, using buttery-smooth-API-silk like
> JQuery, then you are probably feeling a bit cheated.

Sounds like an opportunity for someone who knows how to make a 
"buttery-smooth-API-silk" API for IndexedDB, and hide the complexity of 
the original API. Who could then become an "invited expert" to the WG 
and fix the specification... ;)

JohnK

>
> [1] http://www.html5rocks.com/en/tutorials/indexeddb/todo/#toc-step2
>
> -- Marcos Caceres http://datadriven.com.au
>
>
>
>

Received on Monday, 11 February 2013 16:25:30 UTC