We sped up Notion in the browser with WASM SQLite
1–6 of 6 posts
Re: We sped up Notion in the browser with WASM SQLite
#2Pretty cool. First time I'd heard about the web locks api. https://developer.mozilla.org/en-US/docs/Web/API/Web_Locks_A...
Re: We sped up Notion in the browser with WASM SQLite
#3This part:
> ... the requirement of cross-origin isolation, which would have prevented us from rolling out to any browser beyond Chrome and Edge.
Is incorrect. The primary development browser for the two VFS APIs they're writing about is Firefox. (Citation: that development all happens on my computer.)
Re: We sped up Notion in the browser with WASM SQLite
#4Great write up; but honestly all I could think is what a blunder it was when Mozilla vetoed shipping SQLite.
Re: We sped up Notion in the browser with WASM SQLite
#5This part: > ... the requirement of cross-origin isolation, which would have prevented us from rolling out to any browser beyond Chrome and Edge. Is incorrect. The primary development browser for the two VFS APIs they're writing about is Firefox. (Citation: that development all happens on my computer.)
Blog post author here -- I wasn't totally clear, but what I meant was that we didn't have the capacity to do the work to make Notion fully cross origin isolated (which would have indeed worked on all the major browsers). That meant we could only roll it out on the browsers that provided this temporary workaround for it.
Re: We sped up Notion in the browser with WASM SQLite
#6This part: > ... the requirement of cross-origin isolation, which would have prevented us from rolling out to any browser beyond Chrome and Edge. Is incorrect. The primary development browser for the two VFS APIs they're writing about is Firefox. (Citation: that development all happens on my computer.)
Blog post author here -- I wasn't totally clear, but what I meant was that we didn't have the capacity to do the work to make Notion fully cross origin isolated (which would have indeed worked on all the major browsers). That meant we could only roll it out on the browsers that provided this temporary workaround for it.
Aha, that makes sense. BTW, i would like to reach out to you to discuss, if you like, your corruption cases and pain points so that we can improve upon them. i don't see a way to get in direct touch with you, but if you are up for such a discussion, please email a contact address to stephan at sqlite org.