@wycats @brendaneich That's actually the problem; the stack is limited to the degree that you need the browser vender to let you use SQLite.
-
-
Replying to @landonfuller
@landonfuller No,@wycats' point was that SQLite was like Pepper: single-vendor-impl, code-not-spec, bug4bug compat non-standard.2 replies 0 retweets 0 likes -
-
Replying to @wycats
@wycats@brendaneich Needing vendor support at all for SQLite is the deficiency of the big gap between vendor vs. developer exec environment2 replies 0 retweets 0 likes -
Replying to @landonfuller
@landonfuller@BrendanEich the platform comes with enough primitives to do storage for years.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@brendaneich That's a generous interpretation of 'done' relative to the performance/utility of multithreaded WAL'd-SQLite on native1 reply 0 retweets 0 likes -
Replying to @landonfuller
@landonfuller@BrendanEich I'm also sensing some goalpost moving in this discussion.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@brendaneich Not considering unusable tech demos as viable does not for goalpost moving make.3 replies 0 retweets 0 likes -
Replying to @landonfuller
@landonfuller@BrendanEich "a hypothetical standardized pepper is much better than asm.js + new JS APIs"1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@brendaneich The platforms we have, today, and have shipped apps on for decades, are much better than asm.js + new JS APIs.2 replies 0 retweets 0 likes
@landonfuller @BrendanEich and they can trivially segfault. And require an installation step. No thanks.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.