3 ms·

I doubt I am going to pass it on to someone else as long as I am an end user of the framework. You get a great free framework and I get a framework that works e

I doubt I am going to pass it on to someone else as long as I am an end user of the framework. You get a great free framework and I get a framework that works exactly the way I want it to with the ability to jump into the code at any time and make adjustments that improve it for me. That's the open source deal. He can totally find another maintainer, or a group of maintainers that would do a great job. Kind of selfish of him to hang onto it, tbh.

olingern 10y ago
He could, but I agree with his logic that overall quality of the codebase could degrade without his attention to core. The core project is a result of his ideas and vision, so having others jump in and take over would be difficult. Parse is in a similar state. Stable, maintained by the community, but no longer under a company umbrella. It had a lot of promise, and it's unfortunate Facebook decided to spin it down. A lot of these tools will fall to the wayside as other more efficient, shiny tools replace them, i.e. Angular 1. In general, tool turnover is quite high in the Javascript community. I would expect Hapi to share the same fate as every other Javascript framework that stopped being actively maintained.
wwalser 10y ago
As a user, I'd much rather Eran hold on to control until he finds 3-4 people that he absolutely trusts. Saying no to the 90% of bad ideas and non-issues is one of most difficult and disciplined tasks of maintainership of this type of project. That's coming from someone who recently opened one such non-issue (though my PR was merged to my surprise[1]). 1. https://github.com/hapijs/hapi/pull/3380 https://github.com/hapijs/hapi/pull/3380