I'm a NixOS user and I know Gobolinux is a few years older, this blogpost (from 2011) was actually useful for me at the time when I decided to pick NixOS for my workstations: https://sandervanderburg.blogspot.com/2011/12/evaluation-and-comparison-of-gobolinux.html Nowadays I'm also playing with Guix as well, I kinda love that everything can be unified in a more decent language (Guile Scheme) than Nix:... - Source: Hacker News / 4 months ago

> I started because I wanted Claude Code to manage my system, not just my code. I have two reactions to this. First: respectfully, this is hilarious. LLMs are good at many things, but judgement is not one of them. At the outset, this was firmly in the "terrible ideas" category. Second: sometimes from terrible ideas come great creativity. (I'm actually not sure what epistemic basis creativity flows from, if not... - Source: Hacker News / 5 months ago

If you're interested in what's going on with GNU in general, GUIX is awesome. It's a package manager like Nix but purely GNU (using GNU Guile scheme). It's developed in tandem with the GNU Shepherd init system (instead of systemd/sysvinit/openrc/etc.) and there are distributions based on GNU Hurd kernel (or the Linux-libre kernel). Wikipedia has a pretty good rundown [3] but I recommend booting up a VM image. It's... - Source: Hacker News / 12 months ago

You could take a look at guix [1], it's very much like nix, but is available as a package manager for other distros. [1] https://guix.gnu.org/. - Source: Hacker News / 12 months ago

And then see how it's done in real life: https://guix.gnu.org/. - Source: Hacker News / over 1 year 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 / 5 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 1 month 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 / about 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 / 3 months ago

A typical production stack for teams using Claude or Gemini as the reasoning layer includes an LLM provider API, an orchestration layer (n8n, Temporal, or a custom Python service), application infrastructure (a server running the orchestration code), and a data layer (a database for storing results). Each boundary introduces a failure point. When the LLM provider changes its rate limits, as OpenAI did repeatedly... - Source: dev.to / 4 months ago