--- title: Amiko: A desperate virtue signalling attempt | daily.dev description: Ryan Bigg argues that Amiko, a community fork of Rails created in response to DHH's far-right views, is little more than virtue signalling. He contends that... canonical: https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Amiko: A desperate virtue signalling attempt | daily.dev og:description: Ryan Bigg argues that Amiko, a community fork of Rails created in response to DHH's far-right views, is little more than virtue signalling. He contends that... og:url: https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37 og:image: https://api.daily.dev/og/posts/Ki3U9LP37.png og:image:alt: Amiko: A desperate virtue signalling attempt og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Amiko: A desperate virtue signalling attempt **[RUBYLAND](https://daily.dev/sources/rubyla)** · 5 min read · 0 upvotes · 0 comments ## Summary Ryan Bigg argues that Amiko, a community fork of Rails created in response to DHH's far-right views, is little more than virtue signalling. He contends that simply renaming Rails commands and gems won't overcome Rails' massive momentum, nor will it fix the framework's deep structural problems — namely Active Record's monolithic design, lack of view-layer structure, and absent service object patterns. Bigg points out that a genuine Rails alternative already exists in Hanami (now at version 3), which was built with lessons learned from two decades of Rails development. He urges Amiko contributors to redirect their energy toward Hanami instead. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Amiko and how does it differ from Rails? Amiko is a community fork of Rails created after DHH expressed far-right views. So far it primarily renames Rails components — commands become `amiko` commands, gems like `rails-pack` become `amiko-pack` — while keeping the framework's underlying structure identical. No fundamental architectural changes have been made, meaning Rails' core design problems around Active Record, view helpers, and service objects remain unaddressed. _Ruby developers watching the Rails ecosystem split track forks like Amiko and alternatives like Hanami on daily.dev._ ### What are the main architectural criticisms of Ruby on Rails? Three long-standing structural problems: Active Record provides a single class for all model and database logic with footgun-prone APIs; view helpers are globally shared across all views by default with no scoped alternative; and there is no prescribed pattern for service objects or operations, pushing business logic into controllers or models and making it hard to test in isolation. These issues have persisted from Rails 4 through 8. _Engineers evaluating whether to stay on Rails or move to an alternative find the trade-offs discussed on daily.dev._ ## Similar posts on daily.dev - [Rails is done](https://daily.dev/posts/rails-is-done-bxobwivpz) · RUBYLAND · 3 upvotes · 0 comments - [Issue \#813: A new attempt to fork Rails — Ruby Weekly](https://daily.dev/posts/issue-813-a-new-attempt-to-fork-rails-ruby-weekly-kbcj0j5vw) · Ruby Weekly · 2 upvotes · 0 comments - [Hanami, Why?: Introductions](https://daily.dev/posts/hanami-why-introductions-lrxtqazr0) · Lobsters · 1 upvotes · 0 comments --- Tags: [#ruby](https://daily.dev/tags/ruby), [#rails](https://daily.dev/tags/rails), [#hanami](https://daily.dev/tags/hanami) [View this post on daily.dev](https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Amiko: A desperate virtue signalling attempt","url":"https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37"},"datePublished":"2026-08-08T03:22:45.311Z","dateModified":"2026-08-08T03:23:11.279Z","description":"Ryan Bigg argues that Amiko, a community fork of Rails created in response to DHH's far-right views, is little more than virtue signalling. He contends that...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/301127e3bd70bfd20d19b5a370210fbc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/301127e3bd70bfd20d19b5a370210fbc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"RUBYLAND","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"RUBYLAND","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/rubyla","url":"https://daily.dev/sources/rubyla"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ruby,rails,hanami","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"RUBYLAND","item":"https://daily.dev/sources/rubyla"},{"@type":"ListItem","position":3,"name":"Amiko: A desperate virtue signalling attempt"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/amiko-a-desperate-virtue-signalling-attempt-ki3u9lp37#faq","mainEntity":[{"@type":"Question","name":"What is Amiko and how does it differ from Rails?","acceptedAnswer":{"@type":"Answer","text":"Amiko is a community fork of Rails created after DHH expressed far-right views. So far it primarily renames Rails components — commands become `amiko` commands, gems like `rails-pack` become `amiko-pack` — while keeping the framework's underlying structure identical. No fundamental architectural changes have been made, meaning Rails' core design problems around Active Record, view helpers, and service objects remain unaddressed. Ruby developers watching the Rails ecosystem split track forks like Amiko and alternatives like Hanami on daily.dev."}},{"@type":"Question","name":"What are the main architectural criticisms of Ruby on Rails?","acceptedAnswer":{"@type":"Answer","text":"Three long-standing structural problems: Active Record provides a single class for all model and database logic with footgun-prone APIs; view helpers are globally shared across all views by default with no scoped alternative; and there is no prescribed pattern for service objects or operations, pushing business logic into controllers or models and making it hard to test in isolation. These issues have persisted from Rails 4 through 8. Engineers evaluating whether to stay on Rails or move to an alternative find the trade-offs discussed on daily.dev."}}]} ```