On 4/1/2011 9:39 AM, Aryeh Gregor wrote:
IE6 is closed-source software written for a single platform.  SQLite
is in the public domain, works for all major operating systems and
lots of minor ones, and is already used (I think?) by every major
browser except IE.  That makes all the difference.  There's some
benefit to having multiple interoperable implementations even if the
reference implementation is public-domain, but enormously less than
when the only implementations are controlled by particular parties.
How, exactly, does it make all the difference? I sure hope you aren't suggesting that the spec say "do what this code does."

So if the only objection to WebSQL is "there's no way we're going to
get a formal spec or two interoperable implementations", I'd really
encourage objectors to step back and ask themselves why they *want* a
formal spec and two interoperable implementations.  Those requirements
are not axiomatic, they're means to obtain practical ends like
allowing competitions and avoiding user lock-in.  How many of those
ends are really contrary to using SQLite as a de facto standard, and
do the remaining ones really outweigh the practical advantages?
That's not the only reason.  Mozilla laid out others ten months ago:
https://hacks.mozilla.org/2010/06/beyond-html5-database-apis-and-the-road-to-indexeddb/

Cheers,

Shawn

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to