4 ms·
Google's recent post 'defining openness' seems to be drawing a lot of criticism from Hacker News, both directly in comments, and indirectly in the tone of artic
by numbeast 17y ago
Google's recent post 'defining openness' seems to be drawing a lot of criticism from Hacker News, both directly in comments, and indirectly in the tone of articles that are posted.
First, please recognize that this in an internal memo we are getting a glimpse of. It's a "Hey guys, I know we've been talking a lot about open, here's what I think you should strive to put into a product if you're going to use open to describe the product."
You think it makes Google look perfect? This is an internal memo! He's talking to the troops, have you ever heard a pep talk that started with "We kinda failed on that do no evil thing didn't we?"?
Second, the author specifically mentions why Google doesn't open up certain things, it wouldn't be beneficial. If you don't agree with his reasoning, then fine, but at least we know the reasoning (although it's not hard to figure out on your own).
I simply cannot understand the kind of person that gets angry at Google when they open source some products but not others. How many products has Microsoft open sourced? Yes Google's motives are based on profit, all of our motives are. The point is I'm excited for Android, Go, and Chrome. They have raised the bar in quality software and I couldn't care less how ads find their way to my blog or why Wikipedia is the first search result on any topic.
- bradbeattie 17y agoAn internal memo put on a publicly accessible blog ceases to be internal. It becomes part of PR.
- mpk 17y agoInternal memos appear on publicly accessible blogs all the time :) But in this case they put it on the official company blog, and that makes it PR.