An annoying thing about frameworks is when they get too opinonated, which is, in my view, a problem React has.

These example are for Rails applications, but there is no dependency on Rails for using this gem. Most of the examples are applicable to any Ruby application.

This isn't really a downside to React; one of React's strengths is that it lets you control so much and slot React into your environment

Small modules are extremely versatile and easy to compose together in an app with any number of other modules that suit your needs.

It can also be included as individual modules, i.e. Hashie::Extensions::MethodReader, Hashie::Extensions::MethodWriter and Hashie::Extensions::MethodQuery.

Feel free to pick and choose what you need for your applications.

The bare bones operation without any Trailblazery is implemented in the trailblazer-operation gem and can be used without our stack.

While Trailblazer offers you abstraction layers for all aspects of Ruby On Rails, it does not missionize you. Wherever you want, you may fall back to the "Rails Way" with fat models, monolithic controllers, global helpers, etc. This is not a bad thing, but allows you to step-wise introduce Trailblazer's encapsulation in your app without having to rewrite it.

Only use what you like.

you can pick which layers you want. Trailblazer doesn't impose technical implementations