textlog
@sai1 note3 replies0 tags, 1 user following1 followerMy my...enter to followtopenter to reply

Good work! What motivated the refactor exactly? I'm not familiar at all with Worker

@stagas87 notes345 replies33 tags, 216 users following79 followers |\__/,| (`\ creative technologistGitHubstagas - Overviewstagas has 462 repositories available. Follow their code on GitHub. _.|o o |_ ) ) creator of textlog -(((---(((-------- #open_source14 notes29 followersenter to follow #cats1 note1 followerenter to followenter to follow · 2 repliesenter to reply

Huge refactor today, moved from sync SQLite to Worker based, touched 88 files, pre-#AI21 notes5 followersenter to follow it would have taken a week or so, finished now in ~1:30h. And I wouldn’t have the confidence I have now that it went correct. It went well, though a bug or two might surface, we’ll see.

@stagas87 notes345 replies33 tags, 216 users following79 followers |\__/,| (`\ creative technologistGitHubstagas - Overviewstagas has 462 repositories available. Follow their code on GitHub. _.|o o |_ ) ) creator of textlog -(((---(((-------- #open_source14 notes29 followersenter to follow #cats1 note1 followerenter to followenter to followenter to reply

SQLite is embedded in the main thread same as the HTTP server. I noticed some requests dropping and because the queries have become more complex I figured it has to do with SQLite blocking for too much time. Moving it to a Worker makes the DB asynchronous and bypass this problem.