Dev tools · alternatives · 2026
24 alternatives to Error return traces for Go, inspired by Zig
An alternative to stack traces for your Go errors. Contribute to bracesdev/errtrace development by creating an account on GitHub.
This is a Go library that provides error return tracing inspired by Zig's approach. It helps developers track and display error chains more effectively in Go applications. The tool is designed for Go programmers who… Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. Error return traces for Go, inspired by Zig launched in 2023; newer entries below may have overtaken it.
- 1
Telebugs▲391Hey hackers! In January 2025, I started building Telebugs. It's an installable error tracker that works with Sentry SDKs. I come from a Rails background and previously worked at an error tracking/APM company, so I figured: why not build my own? I wanted a simple, reliable tool I could own outright, without surprise bills for overages. Telebugs is built with Rails 8, Hotwire, TailwindCSS, and SQLite. Like 37signals’ ONCE products (my inspiration), it’s pay-once: prep your hardware, run one command, and you’ll be up and running in 10 minutes (5 minutes refers to the actual installation…
2025 · telebugs.com · its alternatives →
- 2
A path tracer written in Go. Contribute to fogleman/pt development by creating an account on GitHub.
2015 · github.com · its alternatives →
- 3
Hi everyone, I recently published a small open-source project. It’s a minimal network packet analyzer written in Go — designed more like a learning toy than a replacement for Wireshark. It currently supports parsing basic protocols like TLS, DNS, and HTTP, and includes a tiny fuzzing engine to test payload responses. You can inspect raw packet content directly from the terminal. The output is colored for readability, and the code structure is kept simple and clear. The entire program is very small — just about 400 lines of Go code. I know it’s not anywhere near Wireshark’s level, and I still…
2025 · github.com · its alternatives →
- 4
A simple utility for running exhaustiveness checks on Go "sum types." - BurntSushi/go-sumtype
2017 · github.com · its alternatives →
- 5
Helps analyze goroutines. Inspired by TDA for Java and goroutine-inspect for golang. - openziti/goroutine-analyzer
2022 · github.com · its alternatives →
- 6
Minimalist Error collection Service compatible with Rollbar clients. Sentry or Rollbar alternative. - hauxir/errorpush
2021 · github.com · its alternatives →
- 7
- 8
We built Gonzo to make log analysis faster and friendlier in the terminal. Think of it like k9s for logs — a TUI that can ingest JSON, text, or OpenTelemetry (OTLP) logs, highlight and boil up patterns, and even run AI models locally or via API to summarize logs. We’re still iterating, so ideas and contributions are welcome!
2025 · github.com · its alternatives →
- 9
From the creators of rebar3_format, here comes… rebar3_hank, a powerful but simple tool to detect dead code around your Erlang codebase (and kill it with fire!)
2021 · tech.nextroll.com · its alternatives →
- 10
Stack Error is a pragmatic error handling library for Rust that provides helpful messages for debugging, and structured data for runtime error handling. Features: * Informative error messages: stack error messages and optionally add file/line context to your messages. This helps convey not just what went wrong, but also how it went wrong, making debugging faster. * Programmatic error handling: include optional error codes and URIs for robust runtime handling. * Library-Friendly: define custom error types easily while staying compatible with Rust’s error ecosystem. If designing good…
2025 · github.com · its alternatives →
- 11
- 12
A BASIC interpreter written in golang. Contribute to skx/gobasic development by creating an account on GitHub.
2018 · github.com · its alternatives →
- 13
Debugging-friendly exceptions for Python. Contribute to cknd/stackprinter development by creating an account on GitHub.
2019 · github.com · its alternatives →
- 14
Minimal and idiomatic WebSocket library for Go. Contribute to coder/websocket development by creating an account on GitHub.
2019 · github.com · its alternatives →
- 15
Contribute to sendilkumarn/gopurerc development by creating an account on GitHub.
2020 · github.com · its alternatives →
- 16
I believe the best way to learn a language is by doing an in-depth project. This is my first Zig project intended for learning the ropes on publishing a Zig package. It turns out to be quite solid and performant. It might be a bit over-engineered. This little library is packed with the following features: - Building dependency graph from dependency data. - Performing topological sort on the dependency graph. - Generating dependence-free subsets for parallel processing. - Cycle detection and cycle reporting.
2025 · github.com · its alternatives →
- 17ZB
I created this a year or so ago but recently made updates and I thought people might like to know that it exists. I made this to easily send links or text to someone else verbally, like over the phone or over voice chat (which is what I made it for). The goal is to be able to tell the link to someone else without being ambiguous or needing to spell it out, so I grabbed the words off a Grade 5 level dictionary. I understand that the domain itself doesn’t qualify but I’m trying to get a better domain.
2013 · zigg.be · its alternatives →
- 18
An eBPF tool monitoring a goroutine. Contribute to keisku/gmon development by creating an account on GitHub.
2024 · github.com · its alternatives →
- 19
Try/catch/finally in Go. This is an experiment that tries to bring the exception behaviour of java/python/c++ to Golang using the same syntax. - manucorporat/try
2014 · github.com · its alternatives →
- 20
A pretty (simple) alternative to strace. Contribute to JakWai01/lurk development by creating an account on GitHub.
2022 · github.com · its alternatives →
- 21
GlitchTip▲72Simple, affordable error tracking for your project.
2020 · glitchtip.com · its alternatives →
- 22
Doing dynamic dispatching in a strict static typing language is hard. Something as simple as, map.put("add", add); map.put("hello", hello); fn add(a: i32, b: i32) i32 { return a + b; } fn hello() []const u8 { return "Hello World"; } is impossible because the value type of key/value of the map needs to be the same but all the function types are different. Calling functions with different number of parameters, different parameter types, and different return type dynamically is difficult. Other languages either use dynamic typing, runtime reflection, macro, or passing in one big generic…
2025 · github.com · its alternatives →
- 23ZD
Hi everyone, I've made an open-source library for using design by contract (DbC) principles in the Zig programming language. It's called Zig-DbC, and it currently provides the following features: - A simple API to define preconditions, postconditions, and invariants. - Contracts are active in `Debug`, `ReleaseSafe`, and `ReleaseSmall` modes to catch bugs early. - All checks are removed at compile time in `ReleaseFast` mode for zero performance cost. - An optional mode to handle partial state changes in functions that return errors. - Transparent error handling that propagates errors from…
2025 · its alternatives →
- 24
Define and run pattern-based custom linting rules. - quasilyte/go-ruleguard
2020 · github.com · its alternatives →
Also compare
- Telebugs alternatives
- I rendered the Go gopher using Go alternatives
- A toy version of Wireshark (student project) alternatives
- A utility for running exhaustiveness checks on “sum types” in Go alternatives
- Goroutine-analyzer: A visual goroutine stack dump debugging tool alternatives
- Errorpush – Minimalist Sentry alternative using PostgreSQL alternatives
Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →