Strictness in APIs, or "Why Hapi rocks"
You know what I love about Hapi? It's strict.
What does "strict" mean?
It can mean many things. In this case, I'm talking about letting the developer know if he does something which the framework doesn't really understand.
An example is when you have a bug in your code and try to call Hapi's reply() method twice. Hapi can't send a response twice, so it'll let you know. By doing so, it have most likely uncovered a bug in your code. In this case, you might have forgotten a return statement after some error handling logic, for instance.