3 ms·

SQLite is the one project that deserves an exception. There is a near zero chance anyone else can do better with similar quality (and test coverage!) Sometimes

SQLite is the one project that deserves an exception. There is a near zero chance anyone else can do better with similar quality (and test coverage!) Sometimes you need to be pragmatic IMHO.

samwillis 4y ago
SQLite fits one generic model, and is a row level data store. DuckDB is a column store, and other DBs are designed to operate for specific use cases. This is open to all options. The point is that SQLite is a brilliant genetic option, but should not be the only option. WASM and OPFS is the right route forward to enable application developers to use the best data store architecture for their use case. Even within SQLite there are extension that would never have been an available to WebSQL that with this design are.
- treis 4y ago
  But we have 0 options now and 1 is better than 0.
acdha 4y ago
I certainly would agree that SQLite is exemplary but consider how many different things are handled under the aegis of the W3C: if you allow one exception, then you will have other people saying their favorite thing should also have one.
- josefx 4y ago
  So how many implementations of widevine are around? Web standards are well past the point where anyone involved could claim the procedural, moral or intellectual high ground.
  - acdha 4y ago
    The apparent inconsistency here is because you're misunderstanding what Wide Vine is: The standard is Encrypted Media Extensions: https://www.w3.org/TR/encrypted-media/ https://www.w3.org/TR/encrypted-media/ That provides a standard way for web developers to say “Our audio/video files are encrypted. Use this decoder to decrypt the bytes for playback.”. Wide Vine is a popular Content Decryption Module used by EME but it's not the only one (Apple devices use FairPlay, Microsoft ships PlayReady) and the standards process required interoperability to be demonstrated. Web SQL's standardization process halted precisely because nobody was interested in building a second implementation. If Web SQL had a second implementation, it could have been standardized just like EME was.
    - deleted 4y ago
      [deleted]
sfink 4y ago
sqlite> create table numbers (val int); sqlite> insert into numbers values (7); sqlite> insert into numbers values (8); sqlite> insert into numbers values (9); sqlite> insert into numbers values ("hi mom, I'm a number!"); sqlite> select * from numbers; 7 8 9 hi mom, I'm a number! I agree that SQLite is great, but do you really want to standardize on that behavior? People will write applications that insert 41 characters into a varchar(40). And they will care when their sites break when constraints start to be enforced.

SQLite is the one project that deserves an exception. There is a near zero chance anyone else can do better with similar quality (and test coverage!) Sometimes you need to be pragmatic IMHO.

samwillis 4y ago

SQLite fits one generic model, and is a row level data store. DuckDB is a column store, and other DBs are designed to operate for specific use cases. This is open to all options. The point is that SQLite is a brilliant genetic option, but should not be the only option. WASM and OPFS is the right route forward to enable application developers to use the best data store architecture for their use case. Even within SQLite there are extension that would never have been an available to WebSQL that with this design are.

treis 4y ago
But we have 0 options now and 1 is better than 0.

acdha 4y ago

I certainly would agree that SQLite is exemplary but consider how many different things are handled under the aegis of the W3C: if you allow one exception, then you will have other people saying their favorite thing should also have one.

josefx 4y ago
So how many implementations of widevine are around? Web standards are well past the point where anyone involved could claim the procedural, moral or intellectual high ground.
- acdha 4y ago
  The apparent inconsistency here is because you're misunderstanding what Wide Vine is: The standard is Encrypted Media Extensions: https://www.w3.org/TR/encrypted-media/ https://www.w3.org/TR/encrypted-media/ That provides a standard way for web developers to say “Our audio/video files are encrypted. Use this decoder to decrypt the bytes for playback.”. Wide Vine is a popular Content Decryption Module used by EME but it's not the only one (Apple devices use FairPlay, Microsoft ships PlayReady) and the standards process required interoperability to be demonstrated. Web SQL's standardization process halted precisely because nobody was interested in building a second implementation. If Web SQL had a second implementation, it could have been standardized just like EME was.
  - deleted 4y ago
    [deleted]

sfink 4y ago

sqlite> create table numbers (val int); sqlite> insert into numbers values (7); sqlite> insert into numbers values (8); sqlite> insert into numbers values (9); sqlite> insert into numbers values ("hi mom, I'm a number!"); sqlite> select * from numbers; 7 8 9 hi mom, I'm a number! I agree that SQLite is great, but do you really want to standardize on that behavior? People will write applications that insert 41 characters into a varchar(40). And they will care when their sites break when constraints start to be enforced.