Go Programming Language Gets A New Logo and Branding (golang.org)
After an "extensive design process," the Go programming language has a "new look and logo," according to Google's lead for Go developer relations, product, and strategy. (Promising that this won't affect Go's gopher mascot.)
Our logo follows the brand's core philosophy of simplicity over complexity... The circular shape of the letters hints at the eyes of the Go gopher, creating a familiar shape and allowing the mark and the mascot to pair well together... In addition to our brand guide we have also developed a presentation theme. This presentation theme will enable us to have a consistent representation of Go in person at meetups and conferences as well as online.
Go community members are welcome to use this theme for their own presentations. The presentations are available as Google Slides presentations. We chose Google Slides as it is easy to share and maintain updates. People are welcome to port them to keynote, PowerPoint, etc. Like this blog and all our gopher images, the slide themes are Creative Commons Attribution 3.0 licensed... The brand guide, logo and themes are copyrighted by the Go authors. The brand guide contains the guidelines for acceptable logo use.
It's been more than eight years since the language's launch, and "we wanted the Go brand to reflect where we have been and convey where we are going."
Go community members are welcome to use this theme for their own presentations. The presentations are available as Google Slides presentations. We chose Google Slides as it is easy to share and maintain updates. People are welcome to port them to keynote, PowerPoint, etc. Like this blog and all our gopher images, the slide themes are Creative Commons Attribution 3.0 licensed... The brand guide, logo and themes are copyrighted by the Go authors. The brand guide contains the guidelines for acceptable logo use.
It's been more than eight years since the language's launch, and "we wanted the Go brand to reflect where we have been and convey where we are going."
As someone who's written a lot of C professionally- no we wouldn't. Not as an error. As a warning, fine. Preferably one that can be pragma-ed out. But not as an error.
As for formatting- no there really isn't anything good to be said about a consistent style. Especially not to that degree. All you're doing is costing time on meaningless triviality. The time spent to fix it the first time it happens will be an order of magnitude greater than the practical benefits of using the same style for something so trivial for the next 100 years.
I still have more fans than freaks. WTF is wrong with you people?