291–300 of 301 posts
In the original the letters were thinner, and that could have made it feel more lightweight, so it wasn't that bad.
One thing about this new branding is that I have never ever seen Go spelled with all caps (GO). Most only see it as either "Go" or "go". Spelling it with all caps ("GO") makes it look like a single shapeless typographic slab. "Go" is found in text, and "go" is found in code, cmd and everything related. In the original the letters were thinner, and that could have made it feel more lightweight, so it wasn't that bad.
Earlier quoted context omitted.
The logo also appears to have lifted several elements from the podcast Jordan, Jesse, Go [1]. The font is almost identical. It has the white text on almost the exact same shade of blue. It has the three lines trailing part of the logo. EDIT: Here [2] are the two logos side by side. The number of similarities would make this one hell of a coincidence. [1] - http://www.maximumfun.org/shows/jordan-jesse-go [2] - https:/…
Um, no. The updated Go logo is a refresh of the original Go logo when the language was first introduced. https://blog.golang.org/gopher/logo.png
Earlier quoted context omitted.
Ha ha, I tend to agree. In fact, a font that looked like steel or concrete might be good. Wonder if there is one. If so, they could have made the logo to be just the word Go (as I spelled it as regards to case) in that font. Silvery steel font on a gray or black background, or some similar combination. Even a font / image / logo signifying a rugged wood (mahogany or some hardwood?) in some way might have been a good…
Perhaps something like the Google Authenticator logo? https://www.bing.com/images/search?q=google+authenticator+lo...
I'm eager to see how they're going to replace Java little-by-little.
Earlier quoted context omitted.
Perhaps something like the Google Authenticator logo? https://www.bing.com/images/search?q=google+authenticator+lo...
Incidentally, I viewed your above URL for Google Authenticator logo images in mobile a while earlier (after being able to view it fine - with all the images - on desktop PC). And on mobile (Android), amusingly, it seems like Chrome has done its usual optimization of heavy pages (by googleweblight.com or similar means), which often helps save bandwidth and speeds the rendering time, but this time, it resulted in it op…
Reading the comments here makes it clear why most programmers should stay away from design. I've programmed for 20 years now, but that stupid gopher and the way it was everywhere was a serious put off for me on giving Go a look. Nerdy AF. Good riddance. I wonder if there was a huge internal battle between the brand savvy people which realized how terrible the gopher was, and the Go creators. Guys, don't be so stereot…
Earlier quoted context omitted.
Sometimes you want to show your consumer what technologies you used in the product you're selling. The gopher looks very bad on "made with" slides. In a presentation, I had a slide with tons of logos presenting the technologies we used. In the middle of the javascript, html, css and maybe ruby (don't remember), the gopher looked childish and immature. Sometimes it can be ok (if your customer is a young, cool, laid-ba…
Does the customer really care that a product was made with Go instead of C++, Rust, etc? Ruby has a gem and Rust has a rusted R. I guess those are less childish? Java with it's mocha brand is supposed to be professional looking? The customer sees a cup of coffee and thinks to themselves, "Wow, this product is definitely made with professional grade industry standards!".