soumyaray

I have only a fleeting familiarity with Hanami and Trailblazer. It struck me that they are both achieving very similar ends. I preferred Hanami in that it retained very discoverable mechanics for people comfortable with recent low-level trends in webdev (e.g., Interactors are simply Service Objects) while Trailblazer seems to have its own heavily engineered high-level paradigms (e.g., Cells) that seemed more suited to the Rails way of thinking (geminize all the things!). Any paradigms/approaches that Trailblazer advocates that you prefer over Hanami?

I didn't like the magic of Rails either, but didn't grok Python :(

I'm much happier using Ruby + Sinatra + Sequel/ROM + dry-rb

I do admit that Rails devs develop considerably faster than me. But I get a feeling the majority of them can't make much more than a single machine monolith. Rails has a way of narrowing many people's technical curiosities. But it probably behooves both sides to learn more about each other.

Genuine question: Is there any attraction of this tool for folks who already know how to use a static site generator (SSG)? I'm guessing most people who understand how to use git could catch onto an SSG overnight.

(I should add that this is an impressive concept and I'm just begging for a reason to use it).