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 / 14 days 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 / 20 days 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 / about 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 / 2 months ago

The trick is to find whatever metadata channel the queue already gives you and use that and thankfully, almost every mature queue has one (probably because of this scenario). SQS has message attributes, Temporal has context propagators built into the SDK, and Hatchet (which we use to run our workflows) has a metadata field called additionalMetadata. - Source: dev.to / 4 months ago

The "Eve" programming language / IDE - https://witheve.com It was a series of experiments with new approaches to programming. Kind of reminded me of the research that gave us Smalltalk. It would have been interesting to see where they went with it, but they wound up the project. - Source: Hacker News / 10 months ago

Glad someone found it useful! It's at least represents a more fleshed out working example, and it's in a little module so it's pretty self-contained and easy to read through. > I'm assuming this isn't your first go at writing a compiler? Not quite, the first real language I worked on was called Eve: https://witheve.com. - Source: Hacker News / 12 months ago

Other programming languages this author has worked on: Droplet: "Datalog in time and space" - https://github.com/jamii/droplet Eve: "Datalog meets Smalltalk" - https://witheve.com Imp: "An Eve for people who build Eves" - https://github.com/jamii/imp. - Source: Hacker News / over 1 year ago

This reminds me (in the best way possible) of the Eve-lang demos of debugging a program by simply asking "why is not here?" Fantastic work! https://www.youtube.com/watch?v=TWAMr72VaaU&t=164s and https://witheve.com/. - Source: Hacker News / almost 2 years ago

There's also https://github.com/mech-lang/mech . That too seems to be getting close to hiatus. It's a bit of a shame since it seems like quite a nice paradigm for some stuff like GUIs, interactive stuff, and discrete event simulation, but I suppose the paradigm is both a bit obscure and different enough from everything else that it becomes a "boil the ocean" situation where one or a few people try and hack away... - Source: Hacker News / over 2 years ago