MPmpweiher·Apr 5, 2023Submission
3 points · Open discussionbryanp
goru
Ruby2023–2023
bryanp / goru
goru
Concurrent routines for Ruby, without threads or fibers.
2Distinct people
2Mentions
0Explicit recommenders
149GitHub stars
What to know before exploring
What it is
Concurrent routines for Ruby, without threads or fibers.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by 3-hour interval2 dated mentions
Observed mentions: 2023-04-03 13:47:26 UTC to 2023-04-05 17:26:23 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Apr 3, 12:00 | 2023-04-03 12:00:00 UTC | 2023-04-03 15:00:00 UTC | 1 | 1 | 0 |
| Apr 3, 15:00 | 2023-04-03 15:00:00 UTC | 2023-04-03 18:00:00 UTC | 0 | 0 | 0 |
| Apr 3, 18:00 | 2023-04-03 18:00:00 UTC | 2023-04-03 21:00:00 UTC | 0 | 0 | 0 |
| Apr 3, 21:00 | 2023-04-03 21:00:00 UTC | 2023-04-04 00:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 00:00 | 2023-04-04 00:00:00 UTC | 2023-04-04 03:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 03:00 | 2023-04-04 03:00:00 UTC | 2023-04-04 06:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 06:00 | 2023-04-04 06:00:00 UTC | 2023-04-04 09:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 09:00 | 2023-04-04 09:00:00 UTC | 2023-04-04 12:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 12:00 | 2023-04-04 12:00:00 UTC | 2023-04-04 15:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 15:00 | 2023-04-04 15:00:00 UTC | 2023-04-04 18:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 18:00 | 2023-04-04 18:00:00 UTC | 2023-04-04 21:00:00 UTC | 0 | 0 | 0 |
| Apr 4, 21:00 | 2023-04-04 21:00:00 UTC | 2023-04-05 00:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 00:00 | 2023-04-05 00:00:00 UTC | 2023-04-05 03:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 03:00 | 2023-04-05 03:00:00 UTC | 2023-04-05 06:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 06:00 | 2023-04-05 06:00:00 UTC | 2023-04-05 09:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 09:00 | 2023-04-05 09:00:00 UTC | 2023-04-05 12:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 12:00 | 2023-04-05 12:00:00 UTC | 2023-04-05 15:00:00 UTC | 0 | 0 | 0 |
| Apr 5, 15:00 | 2023-04-05 15:00:00 UTC | 2023-04-05 18:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
2 sourcesShow HN: Goru, an experimental, Go-inspired concurrency library for Ruby
Hey folks, wanted to show this off and get feedback. Still early/experimental but there are quite a few concepts I'm excited about here. This project came about while writing a program in Go and loving its approach to concurrency. Being a long-time Rubyist I immediately started to think about what similar concepts might look like in Ruby.
I set out with two main design constraints:
1. Lightweight: I didn't want routines to be backed by fibers or threads. Having been involved some in the async project (https://github.com/socketry/async), I had some experience using fibers for concurrency but was curious if they could be avoided.
2. Explicitness: Routine behavior must be written to describe exactly how it is to behave. I always felt like concurrent code was hard to fully understand because of the indirection involved. On the spectrum betwee
Read the rest
n tedium and magical I wanted to err more on the side of tedium with Goru.
Goru routines are just blocks that are called once for every tick of the reactor. It is up to the developer to implement behavior in terms of a state machine, where on each tick the routine takes some action and then updates the state of the routine for the next tick. This fulfills both design constraints:
1. Because routines are just blocks, they weigh in at about ~345 bytes of memory overhead.
2. Routine behavior is explicit because it is written as a state machine inside the block.
Couple more features worth noting:
* Goru includes channels for buffered reading/writing (similar to channels in Go).
* Goru ships with primitives for non-blocking IO to easily build things like http servers.
Curious your thoughts!