Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we need hapi? #1

Closed
nelsonic opened this issue Feb 4, 2015 · 9 comments
Closed

Do we need hapi? #1

nelsonic opened this issue Feb 4, 2015 · 9 comments
Assignees
Labels
question A question needs to be answered before progress can be made on this issue

Comments

@nelsonic
Copy link
Member

nelsonic commented Feb 4, 2015

Remove hapi?

@nelsonic nelsonic added the question A question needs to be answered before progress can be made on this issue label Feb 4, 2015
@NataliaLKB
Copy link
Member

Does anyone ever need hapi?

@nelsonic
Copy link
Member Author

nelsonic commented Feb 4, 2015

Well, it does provide near-linear horizontal scalability & security out-of-the-box without any extra work... so there are definitely use-cases. the question should have been: can we build a 100-user MVP without Hapi.js?

@NataliaLKB
Copy link
Member

Those are nice features. Not to mention testing seems quite easy so far. I would be happy to use it 👍

@iteles
Copy link
Member

iteles commented Feb 4, 2015

I would also argue that we would learn more about solving problems with relatively little resources (given there's less out there on hapi than on express or vanilla Node). I'm up for the learning curve 👍

@nelsonic
Copy link
Member Author

nelsonic commented Feb 4, 2015

I/we can easily write a sophisticated app in "pure" node http (no frameworks).
But I quite like the testability Hapi provides out of the box...

@NataliaLKB
Copy link
Member

So far more arguments for hapi then against! The only downside with hapi that I have come across so far is because I am not aware of all the 'magic' happening behind the scenes, problems can be hard to debug.

@FilWisher
Copy link

The arguments I hear in favour of frameworks are that
1) teams don't need to talk as much about how to structure code and can start writing their app-specific logic quicker, and
2) large amounts of testing has been done for you.

How does Hapi compare in terms of flexibility with other frameworks? Do we need flexibility? Are there any downsides that outweigh the upsides? I think it would be a mistake to count the arguments for without considering the arguments against.

@iteles
Copy link
Member

iteles commented Feb 15, 2015

I am less keen on lab now than I was before the latest update (from a cursory look over the updates it feels like they've complicated it rather than simplified and that's not a good direction to be heading in), but I hear some pretty awesome endorsements of Hapi itself at scale.

I haven't really written any apps so far that have been totally hammered by concurrent users, but my somewhat inexperienced (and super keen to learn) vote would be for either vanilla Node or Hapi.

@Cleop
Copy link
Member

Cleop commented Feb 14, 2019

Can this issue now be closed @nelsonic given that hapi won't be used in our new version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question A question needs to be answered before progress can be made on this issue
Projects
None yet
Development

No branches or pull requests

5 participants