3 ms·
Isn't that what normally happens when the language has important in-house use cases? >Go has community contributions but it is not a community project. It is G
by GeekyBear 5y ago
Isn't that what normally happens when the language has important in-house use cases?
>Go has community contributions but it is not a community project. It is Google's project. This is an unarguable thing, whether you consider it to be good or bad, and it has effects that we need to accept. For example, if you want some significant thing to be accepted into Go, working to build consensus in the community is far less important than persuading the Go core team.
https://utcc.utoronto.ca/~cks/space/blog/programming/GoIsGooglesLanguage https://utcc.utoronto.ca/~cks/space/blog/programming/GoIsGoo...
- snek_case 5y agoI understand why Apple has a vested interest in maintaining control over the language. What I'm saying is that this puts Swift at a disadvantage in terms of broad adoption and the odds of the language surviving its creator leaving when compared to a language like Rust that has real community involvement and is perceived by everyone as more neutral.
- GeekyBear 5y agoIf you look at the top of the page with Chris' comment, it looks like the Swift team is moving to address this: >In the coming weeks, we hope to introduce a new language workgroup that will focus on the core of the language evolution itself, splitting off this responsibility from the core steering of the project. The intent is to free the core team to invest more in overall project stewardship and create a larger language workgroup that can incorporate more community members in language decisions.