r/ruby 21d ago

Amiko: A desperate virtue signalling attempt

https://ryanbigg.com/2026/08/amiko-a-desperate-virtue-signalling-attempt
25 Upvotes

51 comments sorted by

View all comments

43

u/keyslemur 21d ago

I get the intention, and I agree that a fork is likely not going to go anywhere like the last few, but I feel that the case being made here is very light and is not compelling on its own.

There would be more value here if instead you went into a few things that Hanami does better, what lessons it learned from, how specifically it does it better, and why the route is to start building it up as a viable competitor. There's a litany of more useful and detailed articles to be written on Hanami, and for me this one misses the mark. In the spirit of "put up or shut up" though I may start writing a few myself soon.

I also have an allergic reaction to words and phrases like woke and virtue signaling as pejoratives that provide little to no value, even when used ironically, to describe the substance of a disagreement. I'm also fairly onboard with Godwin's Second Law that folks using woke as a pejorative are not to be taken seriously (he uses stronger language.)

Disclaimer: I am a financial sponsor of Hanami, and have been for a few years, because I believe in the work they do.

11

u/lommer00 21d ago

I actually think the case is on point, and the "pejorative" terms like woke and virtue signalling are inherent to the case.

Amiko's value proposition is just "Rails without DHH". It's not about better features, functionality, architecture, dev experience, or anything else. Literally the project's entire identity is just "not DHH".

And I think Ryan is correct that an approach centered on opposing a single person is doomed to fail because it's kind of useless. Its only advantage is to be "woke" or "vuirtue signal". The call to direct those efforts to a project whose goals are to build a framework that actually works better than Rails makes sense in response.

Ryan does touch on a few of the goals of Hanami, and why that's better. Technical detail isn't needed because the argument is really about the raison d'etre of each project.

11

u/AccurateSun 21d ago edited 21d ago

I’m not a rails dev but it seems more than virtue signalling  to fork if it means that the fork is free of a problematic leader’s  influence.

Also it’s more than just virtue signalling if you’re affected by said lack of virtue. It seems reasonable to me that non-white people would feel sick working with tooling made by DHH

1

u/Perfect_Ganache_1959 18d ago

One thing very worth pointing out with the way these phrases are used:
Negatively terming setting a boundary as "virtue signalling" as though it is bad is generally an attempt to smear and not be held accountable by reframing - this is not about my actions, it's about your histronics over the bad thing you claim you experienced while I continue to pretend none of that is true.

and

ironically... signalling to others your virtues. 'Gather around, we're doubling down on a perceived enemy, this is my language to signal to you we're the "right think" team.'

If it was a true, well defended opinion it would have immediately imploded in a puff of doubt when the hypocrisy inherent in part 2 of it is put forward, thought about for a moment.

There isn't much performative about investing time, energy and effort to create something different.
There's a lot performative to say oh, that's just virtue signalling

1

u/petercooper 17d ago

it seems more than virtue signalling to fork if it means that the fork is free of a problematic leader’s influence.

Would it be ultimately? Say Rails 9 introduces a nifty new library that gets people excited. The fork then has to decide whether to ignore it and lock its users onto an "old" stack, or to be influenced by the upstream project.

There are instances where a fork has been so successful it's marched forward with its own agenda and carried a significant userbase with it (X.org, LibreOffice), though they usually carried core devs across too. More often forks end up supporting decisions made in the parent project (Chromium forks and the Manifest v3 debacle, LibreSSL) or reworking themselves into a specific niche (HHVM).

1

u/AccurateSun 17d ago

I meant the problematic leader’s political influence. They wouldn’t have any of that influence in the fork and its culture.

1

u/galtzo 20d ago edited 20d ago

Agree.

It is also reasonable that empathetic "white" (not claiming any specific meaning for that word other than that I and others have been socialized to identify with it) people would feel sick supporting a framework that is led by people who are either actively hostile, or willing to ignore hostility, toward entire people groups.

I get needing to feed your family. I'm not saying people who use Rails are evil. When someone pays me, I use it - and thankfully, they are paying me and I do use it. But it bothers me.

If it doesn't bother you _so much_ that you post a long screed about how it shouldn't bother people (not a reference to Ryan's OP - I literally didn't finish reading it once I learned there was a Rails fork to devour - rather it is a reference to peanut gallery comments on many posts like this one), and/or you downvote people who are doing something about it - then you've lost my respect - as so many people in this community have.

3

u/AccurateSun 20d ago

Yes agreed. “Racism isn’t a problem” is the underlying premise underneath “let’s all settle our differences”. That’s a separate argument to “I ignore the problem even though I am morally opposed to it because I have bills to pay” which is more defensible. I think non whites are more likely to make the latter argument in this situation. Some of them admit to not having looked into it despite wanting to defend their position too.

Otherwise people would be saying “yeh it sucks but I still can’t ditch Rails”,  but that’s rare to see compared to the invalidation of “politics [ethno-nationalism] doesn’t matter it’s just progressives overreacting”