June 23, 2026

Rails rules? Ruby rebels respond

Rethinking Modularity in Ruby Applications

Ruby devs cheer a fresh layout idea while side-eyeing Rails’ old house rules

TLDR: A new Ruby framework called Syntropy wants app files organized by website paths instead of Rails’ more magical, automatic system. Commenters are into it, especially longtime Ruby developers who say they’ve spent years twisting Rails to fit real projects.

Ruby developers have found themselves in a surprisingly juicy debate over one deceptively simple question: how should an app’s files be organized? The article introduces Syntropy, a new Ruby web framework that lines up files with website addresses, aiming to make apps easier to understand and less reliant on hidden magic. In plain English, the author is arguing that the popular Rails way can feel too automatic: things load behind the scenes, everything lives in one big shared space, and that can get messy when a project grows up and starts having opinions.

The community reaction? Very much “finally, someone said it” mixed with a quieter “careful, we’ve seen reinventions before.” The strongest visible sentiment comes from veteran Ruby folks who sound almost relieved that someone is challenging Rails habits they’ve spent years working around. Commenter chao- basically brings the elder-statesperson energy, saying it’s always exciting to see a new way of structuring Ruby projects and admitting many developers have already been secretly bending Rails to fit real life. That alone tells you the mood: this isn’t just about folders, it’s about longtime frustrations.

The drama is gentler than an all-out flame war, but the subtext is delicious: Team Convention says Rails’ strict rules keep chaos under control, while Team Flexibility says those same rules become a straitjacket. The humor here is classic programmer humor too — less memes, more weary nodding from people who’ve clearly fought their file tree at 2 a.m. The vibe is supportive, curious, and just a little rebellious.

Key Points

  • The article presents Syntropy as a Ruby web framework built around file-based routing, where route handler files are organized according to URL paths.
  • Rails is described as organizing application code through Zeitwerk-based autoloading, with directory structure representing class and module namespaces.
  • The article says Rails’ approach reduces explicit dependency loading but ties class names and file locations closely together.
  • The author argues that implicit dependencies and globally accessible constants in Rails can make large applications harder to understand and test.
  • Syntropy maps directory structure directly to URL namespaces and separates route files from supporting modules stored in directories such as `_lib` and `_layout`.

Hottest takes

"Always cool to see a fresh approach to organizing Ruby projects!" — chao-
"building within Rails and bending it to my desires" — chao-
"a blank-slate pro..." — chao-
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.