> A lot of this boils down to figuring out a delegation model that works for Elm. I agree. This is harder than people think; we've tried some delegation models

> A lot of this boils down to figuring out a delegation model that works for Elm. I agree. This is harder than people think; we've tried some delegation models in the past that didn't go well, and we reverted back to the way things were previously. We're still trying new approaches. The next release will have a core module (Array) written and maintained by a community member (Robin H), and I predict the debugger will be the next core project to fully transition ownership from Evan to a community member. If these go well, they can be models for future delegation to community members! > you're basically asking people to fork your project and what happens after that is unknowable It's pretty predictable though - forks basically always fizzle out unless it's major contributors splitting off (as was the case with io.js), and there aren't factions like that among Elm's most prolific contributors. Turns out it's a lot of work to make something people really want to use!