Congrats on the launch Max and James! We've been in this space for a lil bit too with eesel (https://eesel.app) and it's really cool to see more people tackling these problems. Keen to be inspired and learn! - Source: Hacker News / over 3 years ago

>After a while, we learned that what our users really wanted was to have everything in one place. This is so spot on! We're having similar learnings with eesel [1] too. Work is far too scattered across apps. Thanks for sharing your journey so far and congrats on the launch! [1] https://eesel.app. - Source: Hacker News / almost 4 years ago

You can check it out here https://eesel.app. Source: almost 4 years ago

Not exactly what you're looking for but you could use eesel.app to find pages instead of the address bar. You can configure a deny list for specific pages on eesel.app. The Firefox add on is new - https://addons.mozilla.org/en-GB/firefox/addon/eesel/. Source: almost 5 years ago

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