No post body was provided.
Hanami 2.0
31–40 of 50 posts
Re: Hanami 2.0
#32I come from ramaze (very old, not maintained, very simple), used rails for work (and was never a big fan) and use hanami for a couple of years now. I wrote a wrapper that handles/maintains multiple hanami apps and makes plugin usage easy with multiple projects I use them in. Everything gets deployable with capistrano. I run a few sites with more or less complex features and quite happy with it. Will see how the migra…
I am working on upgrading a few big services from Hanami 1.3 -> 2.0 at the moment. feel free to reach out if you will need some help.
Re: Hanami 2.0
#33Framework-style libraries (i.e. Hanami) pulling in other framework-style libraries (i.e. dry-rb) which themselves pull in other framework-style libraries (i.e. Zeitwerk) is asking for a whole lot of trouble. If your app uses Hanami and Zeitwerk, for example, breaking changes in Zeitwerk may REQUIRE you to update Zeitwerk before you can upgrade Hanami. Or, if dry-rb hasn't adopted the new version of Zeitwerk, you may…
The ruby community is able to do it by having a rigorous set of defaults. When you look at the ecosystem there is far more inter compatibility than say JavaScript/ npm because there are robust norms.
The obsession with magic is actually more an obsession on developer speed and ease because that is the biggest cost and driver of software. The magic also promotes following well tested patterns.
You seem to be advocating a dependency free path where the developer builds everything from scratch. Totally a valid approach but at the cost of development speed and ease. It also results loss of the collective knowledge of a community.
Re: Hanami 2.0
#34Framework-style libraries (i.e. Hanami) pulling in other framework-style libraries (i.e. dry-rb) which themselves pull in other framework-style libraries (i.e. Zeitwerk) is asking for a whole lot of trouble. If your app uses Hanami and Zeitwerk, for example, breaking changes in Zeitwerk may REQUIRE you to update Zeitwerk before you can upgrade Hanami. Or, if dry-rb hasn't adopted the new version of Zeitwerk, you may…
This is the sort of cargo-culty FUD criticism people often bring up about Rails. So many programmers would rather reinvent the wheel, badly, than learn how to use existing products and focusing on their USPs. What would your successor prefer when they take over: Bob's ad-hoc framework built from the ground up where they don't know how anything works, or some app implemented on top of a framework they've used in 10 ot…
Hanami 2.0 is almost completely rewrite in it's core from 1.3, and it took over 3 years. I could not imagine companies relying on owned frameworks - maintaining it, documenting it, educating people to work with them - it's just too expensive.
Re: Hanami 2.0
#35Anyone who knows how this is different from Sinatra and Roda? They seem to be the other two "micro frameworks" (with Rails obviously being the primary Ruby framework).
Hanami aims to be a complete Ruby framework, allowing you to write web apps, but also gems, and non-web ruby applications. Hanami 2.0 only ships for API focus, but in next minor versions this is going to be extended. I see it as a direct alrernative to Rails for anyone who would like to try different style of programming while still using Ruby.
Re: Hanami 2.0
#36This is great! I love Rails but have used Sinatra and Padrino in the past. The knowledge you get using these frameworks can sometimes be brought back to your Rails apps to improve some things. I hope I can have some time in the near future to use Hanami in a real world project. Congratulations to the team.
I agree! My rails applications became way more maintainable since I started being interested in DRY and Hanami:)
Re: Hanami 2.0
#37Earlier quoted context omitted.
Well you can if you want. There's a lot of Ruby projects that are looking for contributions.
Id appreciate if you shared some links or project names. I know it’s a web search away but it sounds like you have some projects in mind. :)
Contributions to Hanami components would be appreciated for sure! There is a whole persistence and views integration to be done fir 2.1 release! The core team will not rest for too long after 2.0 being out :D
Re: Hanami 2.0
#38Earlier quoted context omitted.
Id appreciate if you shared some links or project names. I know it’s a web search away but it sounds like you have some projects in mind. :)
Contributions to Hanami components would be appreciated for sure! There is a whole persistence and views integration to be done fir 2.1 release! The core team will not rest for too long after 2.0 being out :D
Nice thank you. Will follow up.
Re: Hanami 2.0
#39Is...?
Re: Hanami 2.0
#40Anyone who knows how this is different from Sinatra and Roda? They seem to be the other two "micro frameworks" (with Rails obviously being the primary Ruby framework).
Hanami aims to be a complete Ruby framework, allowing you to write web apps, but also gems, and non-web ruby applications. Hanami 2.0 only ships for API focus, but in next minor versions this is going to be extended. I see it as a direct alrernative to Rails for anyone who would like to try different style of programming while still using Ruby.
What benefits does it bring to writing gems?