277 karma · joined September 26, 2010
Second, selling the company puts money in the pockets of the shareholders, while going public means the company is getting the money. Going public, by definition, means revealing your data, your balances, budgets, revenues, it might not look as good as it is now, especially in a bubble-based market.
It's (very) basically like the usual 'let's make a deal' bargain, you can either get 1000$ now, or gamble for the envelope that might have ten times that, but might also have much less.
The only thing a social network has over Google is the ability to perform application-level data cross-referencing, and Google wants a hold in that. Probably before the bubble bursts and those details get lost, or sold, or leaked, or whatever.
As for the "should", they really don't. They could launch they're own LinkedIn-like service, or buy them, or do a different social network, or not. The article keeps hammering that Google have to "win in social". They don't, because, unlike search, there is no, currently, a good way to secure a major share of the market, which is what I'm guessing they mean by "win", because "social" is a bubble, not a real market.
This bubble will burst, sooner or later, and the less Google blows on "social", the better they'll come out of it.
EDIT: apparently not, see below
"It's not even a very good way to learn C. The idioms and best-practices for C programming have evolved substantially, even since the second edition was published, and some of the code samples look a bit dated." And this is from 2004, meaning it got even more dated.(http://sites.google.com/site/steveyegge2/ten-great-books)
The reason K&R is still the canonical C book is because it represents the language better than any other book, before or since, not because the language stagnated since ANSI C was created.
For example, compare Programming Perl (aka the Camel book) to K&R, the former is a long, didactic, journey through Perl's linguistic building blocks, while the latter is a laconic, technical, concise guide to C. I think these also embody the philosophy and nature of these languages. Another example would be Lisp/Scheme books that tend to be academic, and theoretical.
"On the one hand information wants to be expensive, because it's so valuable. The right information in the right place just changes your life. On the other hand, information wants to be free, because the cost of getting it out is getting lower and lower all the time. So you have these two fighting against each other."
Nothing to do with software or products.
I think a much better description of the game, and other chess variants, historical and modern can be found here: http://www.chessvariants.com
EDIT: That article is really golden. It starts with the silliness about not using emacs, without any clear reason why other than "not abiding to Moore's Law" (whatever that means), he praises NetBeans (as if) but claims "almost nobody bothers to modify its code because of its complexity", then, to top it off, ComputerWorld refers to him in that (and other) articles as "Father of Java", ignoring the quote at the bottom that says "People call me that because it pisses me off."
The irony of its all is that Facebook's privacy issues has nothing to do with open/closed source. They can open they're entire source-tree tomorrow, it wouldn't make them more privacy-oriented than now. It's not how they collect the information or how they store it, but what they do with it and with whom they share it.
>"Amateurish failure" pretty much nails it
I think part of the problem here is, as much as those guys have good intention, the whole affair was ill-handled from the start. From the get-go, asking for money before showing any effort made me sceptical of the whole affair. The amount of exposure and money they got, without anything even resembling code, or implementation details was absurd. And then, what they initially came up with could've been done by a few software devs working on their free time, and was riddled by security issues. My advice to those guys is to use the money and hire some good programmers, which is what most startup guys do.
Isn't that what the upvote-downvote system is for?
There's great power in the idea of single assign, and the notion of immutable objects (be it variables, or else) is getting many programmers to rethink their ideas, but saying "this is right because it's like in math" is selling the idea short, and not doing any justice to the strengths of functional programming.
Today, the stakes are not that high. Most of the dirty fights are at the search and user details area. The standards are more strict and developers are fast to call on either side deviations. Lock-in is harder, and, to be honest, it's pretty obvious that whomever the "winner" will be, it won't give them the 99% dominance that IE had at about 2001.
For a start, explain why, in Java, (int) Math.random() is a bug. A programmer that happens upon this thread, now knows "this is bad", but has no clue why. A tool will only make the programmer even more reliant on tools and IDEs, so this kind of bug will be eliminated, but the frame of mind that spawned it will live on.