That’s the number one reason why JB has always declared that Kotlin is “their” language. They have a vision for it, and they want to stay true to that vision.
That said, I’m not sure a proper community board would harm this vision. While it is true that everybody is missing something in the language, if you look at most feature request, most answers are against said feature.
JB’s vision is shared by most of Kotlin’s power users and very few feature requests are actually making consensus. Most of those are either in KEEP or announced either in rodmap or at least being looked into.
For that, I’m not sure. Most of Kotlin’s fame comes really from it’s awesomeness. People use Kotlin because it’s definitely the right choice given their needs and alternatives. I don’t really see what a comunity board would add to that. There are a lot of conferences and “evangelism” done by community members already.
I must remind you of the Node.js / IO.js fiasco… Or the fact that Java’s iterations are so long mainly because of the bloated JCP.
That is probably true
What I think (and have long said) is that I whish JB had a better formal communication with the Kotlin’s community.
It would be great to see more engagement from the community into Kotlin’s future.
It would be great for JB themselves to have a “consulting board” able to summarize what’s important for the community, what we feel are the priority, and how we wish the language to evolve.
Have you noticied that the KEEP repository has been open for 7 weeks, and that the only proposals (both accepted into the process or currently in pull request) are the work of JB workers ?
No community member has drafted a proposal because while the community feels empowered into kotlin’s evangelism, it does not feels the same in Kotin’s future.
A community board would definitely be a good step toward that goal, provided that JB finds the “courage” of letting their baby go… just a little .