Alternatives
Products that do what Dido – .NET framework to facilitate distributed computing does
The project site contains more documentation, but the essential concept tries to answer the question: "What if there was an API similar to the .NET Task Parallel Library but for invoking expressions on other machines, instead of just other threads?". The goal is to allow developers to write, debug, and verify a normal monolithic application, start up a few generic .NET "runner" services, and then quickly and easily add support for distributed execution of specific portions of their code on those runners, without the traditional overhead that comes with explicitly writing and orchestrating…
- 1
- 2
- 3
- 4
- 5
- 6
- 7AD
I'd like to share a project I've been working on for the past few months. It's a distributed workflow engine written entirely in Go. Some highlights: * Tasks are executed in a Docker container * Can run stand-alone or distributed * Highly extensible * Able to enforce limits (CPU/RAM) per task * Web UI Would love the get your feedback on it, and find out if this could be useful.
2023 · github.com
- 8CA
A recent HackerNews comment - “For one programmer's hourly cost, you could run 4000 CPU cores continuously. Can there really be no practical way to apply thousands of cores to boosting the programmer's productivity?” https://news.ycombinator.com/item?id=19339467 This is what we have come up with. The current productivity tools - Slack, Asana, Trello, Facebook Workplace, etc. - are great, but lack direct access to your code. Building a tool directly around the code makes it more powerful for software developers: CoDiff. https://codiff.com The foundation of CoDiff is a…
2019
- 9DT
A few years ago, my team moved from Java to Go. Working on Go projects, we came across a variety of logging frameworks with different APIs outputting messages in different formats. Go seemed to be lacking a logging abstraction like slf4j, which has been so invaluable to the Java ecosystem. Without that abstraction layer, the APIs for configuring logging vary wildly across projects, and libraries must either add a dependency on one of those frameworks or simply avoid structured logging altogether. Dazl is a logging abstraction layer that decouples the logging API from specific Go logging…
2023 · github.com
- 10LS
Hey HN, Lich is a worktree aware local dev stack orchestrator. Simply put, it allows you to run multiple copies of your development stack from different worktrees with different code in parallel without going insane. I built Lich because I’ve found myself increasingly using multiple parallel coding agents for development work. I wanted my coding agents to each have independent copies of my development stack to be able to test and validate their own work well. I found that trying to do this totally broke the way I have normally setup tooling for local development. Ports conflict, the UI from…
Jun 2026 · github.com
- 11WS
The WASI preview 1 specification was missing socket APIs so some WebAssembly runtimes added extensions to allow applications to do more than basic file I/O. This package enables a large class of Go programs (almost any program doing networking) to run when compiled to WebAssembly using the WASI preview 1 spec. It exposes functions similar to net.Dial and net.Listen that can be used to leverage the socket extensions thanks to the new //go:wasmimport compiler directive. It also has a set of examples of how to use popular Go packages when compiling to GOOS=wasip1. Contributions…
2023 · github.com
- 12OL
We built an open source layer to orchestrate multiple Codex agents in parallel. Found myself and some friends running Codex agents across multiple terminals. Thats why me and a friend built emdash. Each agent gets its own isolated workspace, making it easy to see who’s working, who’s stuck, and what’s changed.
Sep 2025 · github.com
- 13FM
I built Frame to better manage the projects I develop with Claude Code, to bring a standard to my Claude Code projects, to improve project and task planning, and to reduce context and memory loss. In its current state, Frame works entirely locally. You don’t need to enter any API keys or anything like that. You can run Claude Code directly using the terminal inside Frame. Why am I not using existing IDEs? Simply because, for me, I no longer need them. What I need is an interface centered around the terminal, not a code editor. I initially built something that allowed me to place terminals in…
Jan 2026
- 14VA
Rather than calling tools one by one, Orion 2 generates a program and runs it end to end, meaning fewer round-trips and lower latency. You can try it out at https://chat.vlm.run When orchestration is code, every workflow is composable, inspectable, and deterministic. We put together a short Orion 2 demo video: https://www.youtube.com/watch?v=rzhXcNAYQ-0
Jun 2026 · vlm.run
- 15
You write a standard solution, just like on LeetCode, and run it through the CLI. It identifies the problem by ID or title, executes your code against local test cases, and shows the result. It currently supports around 1000 problems and multiple languages, including Python, C++, Rust, Java, Go, TypeScript, Swift, and others. The project is still an MVP. System design, SQL, and concurrency problems are not supported yet, but support for more problem types is planned. Made in Haskell!
25d ago · github.com
- 16CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 17RW
Hey HN, I'm Anurag, founder and CEO of Render, a cloud for application developers. We've just launched Render Workflows, a way to define durable tasks by decorating plain TypeScript or Python functions and running them on Render without operating queues, worker pools, retry logic, and state management. Code example below [1]. The use cases we have in mind include agent loops, ETL/data pipelines, billing flows, and other long-running jobs. The model is simple: mark an existing function as a Task, deploy the repo as a Workflow, then trigger runs from your application code or via our API.…
Apr 2026 · render.com
- 18WS
Go v1.21, scheduled for release in August 2023, adds experimental support for the WebAssembly System Interface (WASI). It'll be possible to natively compile server-side WebAssembly applications with Go, making Go a first-class citizen along with C/C++, Rust and Zig. GOOS=wasip1 GOARCH=wasm go build ... WASI is still in preview and is missing some key features, e.g. the ability to create sockets. Some WebAssembly runtimes have taken the initiative to extend the WASI preview, enabling a wider range of applications to run as WebAssembly modules. Today, we're open sourcing our WASI library…
2023 · github.com
- 19LC
Debugging is hard for LLMs, because they primarily depend on source code, and they don't have access to runtime state. I spent countless hours debugging code, and the only way I found LLMs useful for that, is to ask them to add log lines. That's annoying, because it pollutes my code and adds unnecessary diffs. So we made an MCP server that solve this problem. It gives MCP clients (like Claude Code) access to a NodeJS inspector, so they can: 1. set breakpoints 2. step in, step out, continue 3. fetch the current execution location 4. read console output 5. run JS using eval To try: 1. run a…
2025 · github.com
- 20LA
You build LLM applications with YAML files, that define an execution graph. Nodes can be either LLM API calls, regular function executions or other graphs themselves. Because you can nest graphs easily, building complex applications is not an issue, but at the same time you don't lose control. The YAML basically states what are the tasks that need to be done and how they connect. Other than that, you only write individual python functions to be called during the execution. No new classes and abstractions to learn.
2024 · github.com
- 21PO
Hi HN, We are excited to share patchwork - an open-source CLI for dev chore automation that you can use with your LLM of choice. Dev Teams can orchestrate custom workflows (called ‘patchflows’) using a combination of reusable steps and prompt templates to fix vulnerabilities, upgrade breaking dependencies, generate documentation, and more. We built scanning tools in the past, and saw how overwhelmed developers get with their DevSecOps pipelines. LLMs have the potential to help - but there is a need for an 'outer-loop' solution that can be customized to accommodate the processes, priorities,…
2024 · github.com
- 22MG
I'm Evan, CTO of Ito (ito.ai). We do code review that actually runs your code. When we're developing locally, we run lots of coding agents in parallel against the same repo, and we kept hitting the same wall: git worktrees isolate files, but the database, ports, and services all collide. Moo is a brand new internal tool we use to moove faster and thought we'd share it. Every branch or agent attempt gets its own isolated Linux machine, and the machine's state is versioned with your repo. Moo save snapshots the runtime tagged with the current commit. Check out an old SHA, run moo new, and you…
Jul 2026 · github.com
- 23CM
I've been vibe-coding tools to automate chunks of my consulting work, fell down a rabbit hole, and started building actual products. Suddenly I'm in a world of unknown-unknowns and known-unknowns. One of the bigger things to solve was understanding code the LLM generated that I didn't fully grasp. What does it touch? What reads and writes where? Is the auth path where I think it is? So I built codeflowmap. Point it at a repo and it maps the dependency and call graph, then surfaces the read / write / auth paths between files and functions. Connect a local model (Ollama) or any…
Jun 2026 · github.com
- 24AM
I wrote a free book (CC BY license) on software architecture. It classifies architectural patterns / system designs into groups according to their structure, so that each group features a specific set of goals and properties, as structure and function correlate. That results in a kind of inheritance for patterns, making it easy to learn them and even iterate over all the known architectures to analyze their properties. Any feedback and ideas on how to promote the book is warmly welcome!
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →