Alternatives
Products that do what SafePool – Type-safe object pooling for Go does
Frequent memory allocations can be costly in Go. Go's sync.Pool helps with object reuse but isn't type-safe and can introduce bugs. You need type assertions, and it's easy to accidentally return objects twice or forget to return them at all. SafePool provides type safety with Go generics, eliminating the need for type assertions and making pool usage safer and clearer. For objects that need to live across function boundaries, we added PoolManager. It tracks all objects obtained from pools and ensures they're all returned when the manager is cleaned up, preventing leaks across function calls.…
- 1FA
2018 · github.com
- 2AU
2017 · github.com
- 3SC
2019 · conroy.org
- 4
- 5SR
2014 · github.com
- 6IW
Hi HN! During the last few years, I worked on a few applications built with Go, running on AWS Lambda. As I got to know the platform better, I started to find Go & Lambda to be a really productive combination. The applications were fast, and they ended up being much cheaper to run than what my team & I had built before. It’s probably not the best platform for _every_ application, but I was surprised at how much of our workload worked well on it. As we brought new engineers on to our team and helped them get up to speed with the stack, I found that we were covering a lot of the same topics…
2021
- 7GM
I built GoSMig for my own projects and open-sourced it in case it helps others. It’s a tiny generic library (no external deps except golang.org/x/term) for writing SQL migrations in Go with compile-time checks. It supports transactional and non-transactional migrations, rollback, status, version, and a small CLI handler so you can ship your own migration binary. Why another migrator? - Minimal API, no DSL or file layout to learn - Type-safe via Go generics - Works with database/sql and sqlx out of the box - Should work with any db library (or wrapper) that implements some…
Oct 2025 · github.com
- 8PM
2020 · github.com
- 9TI
Spent a week in the break building a pre-compiler that brings type safety to runtime. Still pretty early, but generally does what it says. Looking for feedback, code that breaks it (check out the playground), ideas etc.
Jan 2026 · typical.elliots.dev
- 10GL
2015 · github.com
- 11GG
2017 · github.com
- 12TS
2020 · github.com
- 13TO
2014 · tyk.io
- 14FE
2015 · github.com
- 15AS
Hi HN, I’ve been working on an experimental programming language called XXML. The project started from a frustration I kept running into across systems languages: Languages with strong ownership tend to avoid runtime reflection. Languages with rich reflection usually rely on GC or give up memory guarantees. Compile-time code generation often requires a separate macro language. I wanted to explore whether those tradeoffs are truly necessary. What XXML is trying to do XXML is a statically-typed, native language that: Uses explicit ownership and borrowing (no garbage collector) Supports runtime…
Dec 2025 · xxml-language.com
- 16BO
2015 · github.com
- 17PT
2019 · github.com
- 18AS
Hello, everyone. Three months ago, I started building my first GoLang package, VarMQ. In this short period, I gained a significant amount of traction from the community, and it resulted in over 140 stars on GitHub. A week ago, to check how it performs, I ran benchmarks with a similar package, Pond, which has been managed for years. Pond is not a message queue, though; however, it can be compared to VarmQ since it shares some similarities, except for its storage system. From the benchmarks, I got surprising results, which are that Varmq is taking 50%+ less memory than Pond and also has good…
2025 · github.com
- 19GV
2018 · made2591.github.io
- 20GA
Hello HN! These last few months I've been working on my first open source project: an embedded database written in pure-go. That took me some months, as I had to learn how to deal with such large packages. Until then, all packages I had made were quite small an did not require much. I usually did not have to worry about things like allocation optimization and instance pools until This project. It started when I wanted to make a port of a tool to a TUI environment. I'm actually used to working with TUIs in golang, so that was my language of choice. The tool I wanted to port is written in…
Feb 2026
- 21PB
Hi HN - I’m Peter, here with Max (hmaxdml), and we’re building DBOS Go, an open-source Go library for durable workflows, backed by Postgres. https://github.com/dbos-inc/dbos-transact-golang DBOS workflows make your programs durable by automatically checkpointing their state to Postgres. If your program crashes or fails, all workflows seamlessly resume from their last completed step when your program restarts. This durability makes workflows useful for solving many different problems, including: - Operating an AI agent, or anything that connects to an unreliable or…
Sep 2025 · github.com
- 22GM
I’ve worked a lot with C# and .NET, and one tool I really missed when using Go was AutoMapper. So I built go-mapper, a lightweight Go package that helps map between structs — useful for converting DTOs to domain models, etc. Uses Go generics (1.18+) Supports shallow copy of fields Custom field transformations with fluent API Optional interface for struct-level control Example: type CreateUserDto struct { Name string Password string } type User struct { Name string PasswordHash string } mapper.CreateProfile(CreateUserDto{}, User{}, mapper.ForMember(func(u *User) any { return &u.PasswordHash…
2025
- 23WP
2014 · github.com
- 24RT
2022 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →