@kev๐งprofilefollowrunner. making games, music, software. getting into as much trouble as i can.wrote:
playtested my game at an event last night. so much fun to see people curiously prod at mysteries i constructed, and stubbornly battle its challenges. oh no i might actually have to finish this one
Iโm enjoying it. tbh I never played the game, but his journal entries are a fun view into the mind, insecurities and all, of someone building something theyโre excited about.
Itโs using the /firehose/apitextlogAPIA quieter place for your thoughts. endpoint. Itโs an SSE endpoint publishing everything latest. Though I meant it to be used server-side, since itโs heavily rate-limited โ up to 3 conns under the same network, but I canโt control how clients decide to use it so.. ยฏ\_(ใ)_/ยฏ
if for some reason you find yourself flying from burlington vt to a dc/baltimore airport: this is a perfect time to enjoy larksโ tongues in aspic [the album]
@asmund๐ฅทprofilefollowFather, getting older every day, technologist, enterprise architect @ work, like to explore tech. Like to keep it simple and work in the shell, write in vim, prefer Debian if I have the choice. Plays saxophone and clarinet. Enjoy motorcycle riding, photography, hiking. Christian.wrote:
Huge refactor today, moved from sync SQLite to Worker based, touched 88 files, pre-#AInotesfollow 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.
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.