On Thu, May 23, 2019, at 17:59, Ian Lance Taylor wrote: > But (and here you'll just have to trust me) those executives, and > upper management in general, have never made any attempt to affect how > the Go language and tools and standard library are developed. Of > course, there's no reason for them to. Go is doing fine, so why > should they interfere? And what could they gain if they did > interfere? So they leave us alone.
I wanted to further comment on this particular point, since I keep seeing it brought up and have had it mentioned to me several times OOB in the context of "why would you care if the Go team can push through proposals and immediately merge implementations with limited community input or without the opportunity for alternatives,?Google execs aren't making these decisions, the Go team is!" I believe you when you say that upper management has never interfered with the direction of Go, but the point is that they could in the future. Not having a community check on the Go core team means there is no community check on the future Go core team, or higher up execs that decide they want a finger in the pie. We don't know who will be in charge of the Go team in 10 or 20 years, and they may be less principled than the current team. We also don't know how Google will have changed, or what kinds of pressures might be put on the Go team from a future over- zealous Google executive who wants a hand in the proposal process pie. —Sam -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/1358d19f-b7a6-46db-b970-35c0f7c640d7%40www.fastmail.com. For more options, visit https://groups.google.com/d/optout.
