Conversation

Notices

1. Embed this notice
   alcinnz (alcinnz@floss.social)'s status on Monday, 20-Feb-2023 14:07:19 JST alcinnz

   • David Gerard

   @davidgerard From their discussions, I gather the accusation is that most of the objectors don't actually have a stake in Go.

   I'm sure there's some truth to this, but at the same time I anecdotally see some objectors who do use Go. Not everyone who has a stake engages when they're happy with how the project's going, so determining to what degree that accusation is true is extremely difficult.

   • clacke repeated this.
   • Embed this notice
     Harald Eilertsen (harald@hub.volse.no)'s status on Monday, 20-Feb-2023 14:07:17 JST Harald Eilertsen

     in reply to
     @Adrian Cochrane The thing is that a lot of software written in Go will be deployed using the Go toolchain. As a sysadmin or regular user that just happens to install the occasional app using Go, I'm probably less inclined to even be aware there's something to opt out from.
     clacke likes this.
   • Embed this notice
     CEO of Anti-Clock Society (be@floss.social)'s status on Monday, 20-Feb-2023 14:08:11 JST CEO of Anti-Clock Society

     in reply to

     • David Gerard

     @alcinnz @davidgerard Everyone has a stake in the normalization of opt-out telemetry.

     clacke likes this.
   • Embed this notice
     Björn Lindström (bkhl@social.sdf.org)'s status on Monday, 20-Feb-2023 14:09:21 JST Björn Lindström

     in reply to

     • David Gerard

     @alcinnz @davidgerard I had just kind of gotten around to accepting a plan to start a rewrite in Go at my day job. The alternative is C# and I had just barely been convinced that Go was the least nasty alternative, when this happened.

     That said I still think Go seems more likely to survive as an open source fork than C# if/when the company abandons it, so it may still be the alternative that's the least likely to be a waste of time to learn here ...

     clacke likes this.