Temporal makes durable workflows, activities, retries, timers, failures, and long-running execution explicit. - Source: dev.to / 9 days ago

When a team moves from a monolith into microservices and event-driven, asynchronous systems, it inherits a class of problems that used to be someone else's: work that fails halfway through, steps that must not run twice, calls that return before the work is done. Temporal is a durable execution engine that handles a lot of this - you define a multi-step process, and it guarantees the process runs to completion... - Source: dev.to / about 1 month ago

Durable execution — the pattern implemented by Temporal, Inngest, Rivet Actors, and now Cloudflare Workflows — treats waiting as a continuation rather than a loop:. - Source: dev.to / about 1 month ago

Two specific moves stand out in Duncan's account. The first is durable execution, via Temporal — Mercury replaced fragile cron-and-database state machines with workflow code whose failure semantics are platform-handled (replay, retry, timeout, cancellation). Mercury open-sourced its hs-temporal-sdk, which wraps Temporal's official Rust Core SDK via FFI and provides a Haskell-native API. The dovetail with Haskell's... - Source: dev.to / 2 months ago

We picked Temporal as the first reference engine on purpose. Temporal has the strictest execution model we know of – a V8 sandbox, determinism constraints, replay-driven recovery. If our port contract holds up against that, easier engines – an in-memory test double, a BullMQ queue, or JSON-first platforms like Inngest or Restate – plug in through the same two interfaces. We're shipping Temporal first; the rest is... - Source: dev.to / 3 months ago

As the author of QuickTile, which is written in Python but even closer to what you describe than a window manager would be, I have to say that, yeah, doing X11 stuff takes a lot of knowledge that's not ideally documented in non-print sources. Source: over 3 years ago

Actually, I plan to add a .nojekyll file and then use something like Pelican with custom plugins, then set GitHub Actions to run my update.sh on push... Similar to how http://ssokolow.com/quicktile/ is a Sphinx-based site hosted on GitHub Pages and automatically regenerated from the pushed sources. Source: over 4 years ago

I've been using ssokolow.com/quicktile for this purpose, it does what I need and doesn't replace the wm. Source: over 4 years ago

The best I could do for the API documentation for this project of mine was to use the automodule directive to autogenerate at the coarsest level possible and remember to never create new .py files if I could possibly avoid it. Source: about 5 years ago