HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
amatsuda
rubish
Ruby2026–2026
amatsuda / rubish

rubish

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
300GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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, 3:56:07 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 hour2 dated mentions

Observed mentions: 2026-05-23 06:32:00 UTC to 2026-05-23 12:26:59 UTC.

012026-05-23 06:00:00 UTC to 2026-05-23 07:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 23, 06:002026-05-23 07:00:00 UTC to 2026-05-23 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-23 08:00:00 UTC to 2026-05-23 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-23 09:00:00 UTC to 2026-05-23 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 23, 09:002026-05-23 10:00:00 UTC to 2026-05-23 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-23 11:00:00 UTC to 2026-05-23 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-05-23 12:00:00 UTC to 2026-05-23 13:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 23, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 23, 06:002026-05-23 06:00:00 UTC2026-05-23 07:00:00 UTC110
May 23, 07:002026-05-23 07:00:00 UTC2026-05-23 08:00:00 UTC000
May 23, 08:002026-05-23 08:00:00 UTC2026-05-23 09:00:00 UTC000
May 23, 09:002026-05-23 09:00:00 UTC2026-05-23 10:00:00 UTC000
May 23, 10:002026-05-23 10:00:00 UTC2026-05-23 11:00:00 UTC000
May 23, 11:002026-05-23 11:00:00 UTC2026-05-23 12:00:00 UTC000
May 23, 12:002026-05-23 12:00:00 UTC2026-05-23 13:00:00 UTC101

What Hacker News says

2 sources
I'm recently seeing more and more Ruby projects that are at least partly vibe-coded, and I'm kind of torn. On the one hand I appreciate that this allows people to create stuff that they maybe wouldn't have the time to do otherwise. On the other, the code itself makes it harder for people to contribute, especially those, like me, who don't use coding agents. A random example: https://github.com/amatsuda/rubish/blob/master/lib/rubish/pa... Where are the interface boundaries? Why are there methods that are 200 lines long? This is not a dis at the author, and it's not really about "code quality" per se, whatever that means. It's just that if someone would like to study the code and be able to improve it or add features, how would one go about it? Does this mean you have to use a coding agent in order to contribute? I felt the same about the r
Read the rest
ecent Ruby compiler from matz [1]. The code looks impenetrable. What does this bode for the future of OSS? [1] https://github.com/matz/spinel
In Rubish: A Unix shell written in pure Ruby

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.