We Want to Move Ruby Forward
Posted2 months agoActive2 months ago
andre.arko.netTechstory
calmpositive
Debate
20/100
Ruby Programming LanguageSoftware DevelopmentLanguage Evolution
Key topics
Ruby Programming Language
Software Development
Language Evolution
The author discusses the need to move the Ruby programming language forward, sparking a discussion on the language's future and potential improvements.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
5h
Peak period
3
0-6h
Avg / period
1.5
Key moments
- 01Story posted
Oct 26, 2025 at 2:31 AM EDT
2 months ago
Step 01 - 02First comment
Oct 26, 2025 at 7:44 AM EDT
5h after posting
Step 02 - 03Peak activity
3 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Oct 28, 2025 at 4:13 PM EDT
2 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45709585Type: storyLast synced: 11/20/2025, 2:09:11 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Andre's new condition is to have a "legal agreement" to settle "legal claims". I suppose a court of law looks unfavorably upon him registering a false trademark and ssh'ing into a former company's service from a foreign country (among other acts).
Partly due those revelations, Andre's supporters seemed to have simmered down recently. I assume word has put out that further oversharing and politiking would be legally consequential.
So... not the entire Ruby community. And specifically not people who put in the work so far. What is with this weird phrasing?
- Matz letting things evolve too much on their own since the beginning of Ruby and not carefully adding new features. People made fun of it because there are too many ways of doing things (bloat).
- I think DHH did a great job, but then he let go too much to the wrong people.
- All the Zed stuff, massive changes in Rails in 4.x, then Ember (adapters to well-used frameworks would’ve been so much better), then 7 was just too different.
- Ruby 2.7.7 / poor handling of mac amd arch. This killed it for me.
- MRuby and Crystal.
- When Rails lost a big part of the community to Elixir.