41–50 of 301 posts
The logo and the philosophy behind it are the first things anyone, professional designer or not, would think of. If Go's philosophy was to implement the first thing that comes to mind, it would have generics by now :) I think they need to put a little more thought into this.
Edit: Maybe the design could could incorporate a visual representation of goroutines in some way?
Perhaps this won't be a popular sentiment, but since when did programming languages need brand identity?
Looks like they are loosing the bespoke Go fonts ( https://blog.golang.org/go-fonts ) and going with Work Sans and Roboto. I understand the reasoning. Personally, I have a big soft spot in my heart for the go fonts . Whenever I feel like coding like it's 1979 again, I load them up in my editor and pretend I'm looking at well written documentation from my childhood. [edit: Yay, Go fonts remain for source code display!…
The circular shape of the letters hints at the eyes of the Go gopher, creating a familiar shape I found it agreeable, woody, complex and balanced, with notes of ash and clover.
Sleek new logo makes it look like a bicycle renting start up. While I think its good to refresh branding and aim to unify more things, I will miss the Go Gopher.
Renee French, the original illustrator of the Go Gopher, is still updating the gopher: http://reneefrench.blogspot.com I'm partial to this take on the little fella: http://reneefrench.blogspot.com/2016/11/blog-post.html
Sleek new logo makes it look like a bicycle renting start up. While I think its good to refresh branding and aim to unify more things, I will miss the Go Gopher.
The gopher didn't go away. You can find it on pages 21 & 22 of the new Brand Book: https://storage.googleapis.com/golang-assets/go-brand-book-v...
Perhaps this won't be a popular sentiment, but since when did programming languages need brand identity?
Languages do need to develop a critical mass of resources related to them, people need to provide services for them, and you do want to identify which ones are official. For that purpose, a brand identity is going to be helpful. (At least as helpful as a brand can be.)
In a nutshell, it's about ensuring people can distinguish between golang.org and w3schools.com.
Looks like they are loosing the bespoke Go fonts ( https://blog.golang.org/go-fonts ) and going with Work Sans and Roboto. I understand the reasoning. Personally, I have a big soft spot in my heart for the go fonts . Whenever I feel like coding like it's 1979 again, I load them up in my editor and pretend I'm looking at well written documentation from my childhood. [edit: Yay, Go fonts remain for source code display!…
Just checking, but did you see page 19?