to switch code and framework parts. Do you want to change model to AR or ROM? No problem, it’s easy. Do you think that there is too much of hanami ? You can use just routes.
on production application faster. I want to ask few questions: • Who read at least one book about sinatra or grape? • about rails? • And who read more than five books about rails? I think I read five different books about rails. Framework is just a tool, don't make a cult of it
recommend a monolith- first strategy. And hanami has a simple way to create monolith apps. This way is called Application Architecture. It looks like a typical rails application
gem together and provides CLI • router - Rack compatible HTTP router for Ruby • controller - Full featured and fast actions for Rack • utils - Ruby core extensions and class utilities • model - Persistence with entities and repositories
objects • helpers - View helpers for Ruby applications • view - Presentation with a separation between views and templates • assets - Assets management for Ruby • mailer - Mail for Ruby applications
example I use block notation instead of class. it's logical to compare rails action and hanami action. And I have a really good example of rails action
with templates and instance variables which we call in our templates. Also we have helper modules. I think that everybody in this room knows that rails helpers have some problems. For example a few days ago I got a bug when one person initialized three methods with one name and after that he had problems.
is a typical ruby class where you can put all your? view logic and call this in templates. Also we have templates and also hanami has getters from controller instead instance variable. so and the last part
years old and Sinatra is 8.That's why some useful gems are missing.And I think you can’t create a blog for 15 minutes because many parts you‘ll have to create manually
with all of this I have some bad news for you. Hanami doesn’t support all of this.But if you want to try to use it, don't forget a developer’s manifesto
I created empty rails and hanami applications. After that I added two actions for each application. first action responde view, and second api. Draw your own conclusions.
your urls. Well, you have more coding but it brings you positive feelings. Now I can say that my next api will be on hamani. I really love controllers and models realisation
, typical admin pages are a very bad part of hanami projects. You need to work with assets and with views and now it is still raw. But I hope that in the future it is going to be much better.