tunny
semaphore
| tunny | semaphore | |
|---|---|---|
| 3 | - | |
| 3,914 | 103 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 2 years ago | almost 5 years ago | |
| Go | Go | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tunny
-
Show HN: Rill – Composable concurrency toolkit for Go
There are also libraries like https://github.com/Jeffail/tunny or https://pkg.go.dev/go.uber.org/goleak or https://github.com/fatih/semgroup to help deal with concurrency limits and goroutine lifecycle management.
As the author of https://github.com/ahmetb/go-linq, it's hard to find adoption for libraries offering "syntactic sugar" in Go, as the language culture discourages those kind of abstractions and keeping the code straightforward.
-
Help! channel vs workerpool
https://github.com/Jeffail/tunny uses interface, os it's a no for me
-
Show HN: Tasqueue – A simple, customisable distributed job/worker in Go
Is this a more advanced version of Tunny [0]?
[0] https://github.com/Jeffail/tunny
semaphore
We haven't tracked posts mentioning semaphore yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
ants - 🐜🐜🐜 ants is the most powerful and reliable pooling solution for Go.
workerpool - Go simple async worker pool
go-do-work - Dynamically resizable pools of goroutines which can queue an infinite number of jobs.
go-waitgroup - A sync.WaitGroup with error handling and concurrency control
goworker - goworker is a Go-based background worker that runs 10 to 100,000* times faster than Ruby-based workers.
neilotoole/errgroup - errgroup with goroutine worker limits
grpool - Lightweight Goroutine pool
go-floc - Floc: Orchestrate goroutines with ease.
Goflow - Simply way to control goroutines execution order based on dependencies