when I saw that post a year ago, i thought that you can postpone scale issues with a cdn for a good long while if you could find a mechanism to update the sqlite chunks in a predictable user-friendly way. it’s quite an innovation.

after some meditation, i opted to do something simpler. if i was going to delay the the write consistency anyway, it’s just easier for the user to just download a lagging html file. this definitely depends on the use case, but i avoid a lot of this wasm js complexity by just having the browser download a static eventually updated html file