[08:22:09] ryankemper: I haven't thought about the benefits of weekly restarts indeed... not sure how to deal with that tho... [08:43:33] if weekly restarts are really a benefit, we can automate those. It always feels like a failure to automatically restart a service regularly, but if that's what we have to do... [08:43:58] Or just do a manual restart weekly in the meantime. That's already less work than a full deployment. [10:34:57] Lunch [10:48:24] lunch [11:46:27] errand [12:59:00] back [13:09:45] greetings [14:00:26] inflatador: https://defkey.com/jetbrains-intellij-idea-macos-shortcuts [14:01:12] inflatador: ping me if you need a review on that spicerack CR [14:08:20] gehel ACK, thanks [14:51:35] Here's some analysis of newer/more obscure search engines: https://dkb.io/post/the-next-google [15:01:33] office hours are starting, we already have one guest who has joined: https://meet.google.com/vgj-bbeb-uyi [16:07:39] workout, back in ~30 [17:04:53] sorry it took so long, had to help my wife load up some stuff [17:53:31] dinner [18:15:33] cross posting some search research findings from slack: https://docs.google.com/document/d/1rtNrpxDFyTHRre2S5ld4H_VqLYfXWKJ1H-hW80QCDz8/edit# [18:19:06] is search performance better if we are displaying fewer results? I'm thinking about the go bar, and how there may performance issues constantly searching after every keystroke. But if we waited for a longer user action delay and only displayed the top search result as a suggestion, is that more viable performance-wise than doing a full search? [19:04:36] nice, thanks for linking [22:02:20] See you tomorrow!