go-workflow uses same model as the Workflow SDK, in Go.
“use workflow” is a runner, “use step” is a step function, Promise.allSettled is workflow.Join.
Here’s the same example, ported 👇
Next for go-workflow is native support in the Vercel dashboard. Would love to make that happen.
@cramforce @pranaygp
1
29
Introducing go-workflow: durable workflows for Go, inspired by the Workflow SDK.
Write a workflow as a plain Go function. Each step’s result is persisted, so a run survives crashes, restarts, and deploys, and continues exactly where it stopped.
1
1
56
Every World serves an HTTP endpoint, and the go-workflow/world-http adapter connects the Workflow SDK CLI and web UI to it.
Inspect Go runs, steps, events, and streams in the same web UI the Workflow SDK uses:
npx workflow web
1
6
Introducing go-dev, a code driven development task runner that lives in your go project. It rebuilds your app on code changes, handles soft replacements. For web apps it supports auto refresh using vite.
Start your dev server as simple as `go run ./dev`
github.com/eriicafes/go-dev
Eric Afes retweeted
new post: the senior engineer death spiral
sunilpai.dev/posts/the-senio…
a friend just started a big job and asked for some advice. so I braindumped a monologue about a super common failure mode I see with engineers and posted it here, hope it helps whoever it can.
I admire the simplicity of solid 2.0 around async. I like this a lot
Part Two of @RyanCarniato's in-depth look at Solid 2.0's Async shows how having the right primitives lets you skip the rewrite.
Your client-only app was the optimistic UI all along. It just wasn't aware of the server yet.
solidjs.com/blog/async-solid…
2
65









