I still want to know what made you think Go is a "community project".
Well, the main developers do listen to the community.
Any project can fork, if there are enough people who are very dissatisfied with the current management.
I'm not aware of any serious grumblings about such a fork though. Why?
The core team is very good, and very narrowly focused. They've communicated clearly on nearly every issue as to what they're doing, and why. It seems clear that they are intent on making the best possible tool that fits with their particular vision. There are people who agree with this vision, and broadly support their efforts. And then there are people who really don't like their vision, and wander off to use Rust or something else.
The core team has enormous respect from the existing golang community. If Google suddenly laid off the developers (or just switched them to something else) or otherwise dramatically changed direction in their support for the project, the community would move in quickly to help out the situation.
I could see people getting together to form a non-profit foundation that could at least pay for a few guys to continue to work on Go full-time. But currently, there is no apparent need, so it hasn't been done. Google is willing to pay substantially for the development, and I don't see gophers complaining about that.
> I could see people getting together to form a non-profit foundation that could at least pay for a few guys to continue to work on Go full-time.
It's not going to happen, for the same reason the biggest startups in the Silicon Valley never came together to write their own language before. Let's get things straight, the only people who control Go is the Go team period. You are not talking about facts, so i'm not sure what is the point of your comment.
The point I was trying to make is that the golang community has a lot of respect for the current core team. If the community didn't have that respect, then I speculate that there would be a fork (or takeover), and it would then look more like the kind of community-controlled project that you seem to prefer.
This kind of thing has happened in the past: XFree86, OpenOffice, gcc, etc.
Well, the main developers do listen to the community.
Any project can fork, if there are enough people who are very dissatisfied with the current management.
I'm not aware of any serious grumblings about such a fork though. Why?
The core team is very good, and very narrowly focused. They've communicated clearly on nearly every issue as to what they're doing, and why. It seems clear that they are intent on making the best possible tool that fits with their particular vision. There are people who agree with this vision, and broadly support their efforts. And then there are people who really don't like their vision, and wander off to use Rust or something else.
The core team has enormous respect from the existing golang community. If Google suddenly laid off the developers (or just switched them to something else) or otherwise dramatically changed direction in their support for the project, the community would move in quickly to help out the situation.
I could see people getting together to form a non-profit foundation that could at least pay for a few guys to continue to work on Go full-time. But currently, there is no apparent need, so it hasn't been done. Google is willing to pay substantially for the development, and I don't see gophers complaining about that.