I think the author is handling "not having time to maintain it anymore" well. Rather than just throwing up his hands, he's offering a clear and disciplined economic argument, and a way to balance the equation back in favor of the project.

Despite the blog post, hapi.js has only 8 open issues, 2 of which are bugs. Seems like they've done a good job maintaining a stable framework.