Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hanami 2.0

hanamirb.org

Post reply on HN
Print view View original

41–50 of 50 posts

Re: Hanami 2.0

#41

Post by lukeasrodgers »

revskill wrote: post #27
solnic wrote: post #24

Earlier quoted context omitted.

You missed the context of this example - it's just there to show that IF you don't want to use constructor DI, you can put things in lib and they won't become part of the automatic DI system

The point here, is, let's code in production. No good production code allows such things to accidentially happen, so to me, it's the error from framework. What's the point of using a framework if it couldn't help me do silly things then ?

How would Hanami prevent this without messing with ruby constant lookup? Probably monkey patches to Kernel would be required.

Re: Hanami 2.0

#44

Post by PikachuEXE »

1letterunixname wrote: post #43

dry is a neat framework. It also works with rails. [0] 0. https://dry-rb.org/gems/dry-rails I'm sad that the trailblazer stack went so commercial as to be FOSS-hostile and unusable.

trailblazer - Besides the cells gems I used soon since it's created (before trailblazer became a thing) I have never used others

I found that some doc are removed from README to a 3rd party website which seems odd to me

Re: Hanami 2.0

#45

Post by hanamimastery »

revscat wrote: post #40
hanamimastery wrote: post #35

Earlier quoted context omitted.

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?

Similar to what rodauth did, or active-admin - extracting mountable, shareable and reusable parts of your app to a separate thing.

Re: Hanami 2.0

#46

Post by revscat »

hanamimastery wrote: post #45
revscat wrote: post #40

Earlier quoted context omitted.

What benefits does it bring to writing gems?

Similar to what rodauth did, or active-admin - extracting mountable, shareable and reusable parts of your app to a separate thing.

Is this documented somewhere? Sounds interesting.

Re: Hanami 2.0

#47

Post by entropie »

hanamimastery wrote: post #32
entropie wrote: post #28

I 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.

I bet some more people are interested in howto and your experience. Maybe a gist or some blog post?

Re: Hanami 2.0

#48

Post by bjeanes »

Looks like the new 2.0 guides doesn't have anything regarding views and templates yet. Is that a documentation gap or is it like some of the closer ROM integration, where it will be 2.1 where that is functionally fleshed out?

Re: Hanami 2.0

#49

Post by solnic »

bjeanes wrote: post #48

Looks like the new 2.0 guides doesn't have anything regarding views and templates yet. Is that a documentation gap or is it like some of the closer ROM integration, where it will be 2.1 where that is functionally fleshed out?

Yes the view layer will be introduced in 2.1. We have hanami-view ready but we need to build hanami-assets and hanami-helpers + add integration code to the main hanami gem.
Post reply on HN