Temporal and DBOS are more around the durability guarantees. If you have tasks that are expensive to restart from scratch, or if you have human-in-the-loop approvals, or you have months between steps (e.g. 90-day warranty inspection after installation), you want that durability.
I was excited about this idea, but based on the writing patterns and vague stories I'm pretty sure these writeups are mostly AI slop. For example, this is classic ChatGPT phrasing:
> The growth I’d been celebrating wasn’t real growth—it was just a spike of first-time buyers who never came back.
If I'm wrong, and these were actually written by a human, I'd love a chance to stand corrected and apologize.
My favorite section in an RFC is "alternatives considered". I've seen many times that an option that had been initially discarded became the solution after review and discussion. It's also a great way to answer later questions about "why didn't you do X instead".
Just imagine being the designer of this thing and sitting at Thanksgiving dinner with your family. "Oh, tedchs, what've you been up to at work?" "Okay well this is gonna sound odd but we invented a camera for your stool... No, not that stool... Yes, it clips onto the bowl..."
My question is, why can Google themselves not just provide a dump to archive.org themselves? Having volunteer middlemen doing the work seems like an artificial crisis.
I've used strings of Twinkly lights for a couple seasons now. They can sometimes be found on eBay for cheap. They're easy to set up, whether standalone or by clustering multiple units into one larger virtual canvas. The app has a lot of good looking animated patterns included.
I've had the reMarkable 2 for years and it's amazing. FYI, the reMarkable is itself quite hackable. There is a supported way to run an SSH server on it and push your own binaries and other files to use on the device. One example resource for hacks/mods is https://github.com/danielebruneo/remarkable2-hacks .
reply