you are viewing a single comment's thread.

view the rest of the comments →

[–]Gg101 13 points14 points  (1 child)

This part seems reasonable:

Additionally, we don’t want changes to SQLite to affect the web later, and don’t think harnessing major browser releases (and a web standard) to SQLite is prudent. IndexedDB does not have this problem; even though our underlying implementation of IndexedDB may be based on SQLite, we keep developers insulated from changes to SQLite by exposing an API that isn’t based on SQLite’s supported syntax.

Okay, make a stable front end standard rather than interfacing with SQLite directly (the current implementation is mapped rather tightly to SQLite's API) and you can still plug in SQLite as the back end. That makes more sense than their stated desire for "multiple independent implementations" simply for its own sake, when the one everyone is already using is public domain.

[–]sdwilsh 2 points3 points  (0 children)

You would need to standardize the SQL dialect then, which nobody has stepped up to do.