3 ms·

Hey Nolan, It was good to "meet" you at edgeconf (really we were just throwing the mic back and forth, and I couldnt make it to the afterparty). I really enjo

Hey Nolan, It was good to "meet" you at edgeconf (really we were just throwing the mic back and forth, and I couldnt make it to the afterparty). I really enjoyed your panel intro and insight. I agree with your assessment that IndexedDB is laughably bad in Safari, but maybe they haven't bothered because its really not such a great solution in general? I'm going to reassert that I think we could do much better - since IndexedDB is too low-level for what it is, but too specific for alternate solutions. I've been kicking around a blog post that I haven't got out yet - but we really need something more stream like and generic than a NoSQL index in the browser - especially something fundamental to address the future influx of WebAssembly apps. Cheers!

Touche 11y ago
> I agree with your assessment that IndexedDB is laughably bad in Safari, but maybe they haven't bothered because its really not such a great solution in general? So where's their alternative spec?
nolanl 11y ago
I still have a soft spot for WebSQL over IndexedDB - way easier to work with, incredibly powerful, brought the speed and reliability of SQLite. However, WebSQL only ever managed to have one implementation (Chrome and Safari shared WebKit at the time), and the other vendors besides Opera didn't want to touch it. So it's long since time to accept that it's dead. What bothered me most about the IndexedDB fiasco with iOS8 is that Apple not only held out for so many years, but then they deployed a broken implementation. Anybody who had written an app using an IndexedDB shim either had a crashed site at best or lost user data at worst. YDN-DB author Kyaw Tun had the best quote: "I don't understand how they can release this." Whether you like an API or not, a browser vendor should at least release it in good faith if they're going to release it.

Touche 11y ago

> I agree with your assessment that IndexedDB is laughably bad in Safari, but maybe they haven't bothered because its really not such a great solution in general? So where's their alternative spec?

nolanl 11y ago

I still have a soft spot for WebSQL over IndexedDB - way easier to work with, incredibly powerful, brought the speed and reliability of SQLite. However, WebSQL only ever managed to have one implementation (Chrome and Safari shared WebKit at the time), and the other vendors besides Opera didn't want to touch it. So it's long since time to accept that it's dead. What bothered me most about the IndexedDB fiasco with iOS8 is that Apple not only held out for so many years, but then they deployed a broken implementation. Anybody who had written an app using an IndexedDB shim either had a crashed site at best or lost user data at worst. YDN-DB author Kyaw Tun had the best quote: "I don't understand how they can release this." Whether you like an API or not, a browser vendor should at least release it in good faith if they're going to release it.