cllns_ruby

7 ms·

1.
by cllns_ruby 3mo ago
Sorry to hear about that. We definitely can't protect developers from themselves. Over-engineering is definitely a risk to be aware of and guarded against. We provide powerful tools that can help your codebase, but they can also be mis
2.
by cllns_ruby 3mo ago
Hanami's DB layer was completely rewritten for Hanami 2 (based on Rom, and we've since merged teams), so you should try doing these again! Rom has some other advantages, like not needing a 1-to-1 mapping between tables/column
3.
by cllns_ruby 3mo ago
Taking a workshop at Rocky Mountain Ruby on "Component Based Rails Applications" with Stephan Hagemann (the author of that book) was my introduction to all of this stuff! I found Hanami (then called Lotus) shortly after and I neve
4.
by cllns_ruby 3mo ago
Thanks! Hanami doesn't have any specific Inertia or Svelte specific integrations, but our view layer (and assets layer) is very flexible so it's certainly possible. It's worth investigating. If you try it out, let us know wha
5.
by cllns_ruby 3mo ago
Definitely on the roadmap! I've also run into some rough edges with Rom and we want to fix those all up in a new version. We were just prioritizing Hanami 3 for the medium term, but hopefully we can focus efforts on Rom soon.
6.
by cllns_ruby 3mo ago
Completely agree! I did most of this work and I wanted to add before-and-after benchmarking but I got busy. I have an in-progress (private for now) implementation of the Medium clone RealWorld [1] project. I want to make that public with so
7.
by cllns_ruby 3mo ago
Hanami core team-member here :) We re-did our homepage recently, and we should make these things clearer. They're legitimate concerns and questions. We agree you don't have to write bad code in Rails, and we don't pretend tha