Skip to main content

Distributed Battle of the Giants

Google and Yahoo are facing each other on a lot of battle grounds, and some of them are less public than others. Research is key to the long term survival of both companies, and lots of information is the bread and butter of the two. Without effective technology to burrow through unheard of volumes of data in record time, neither will make it. Some of the things coming out of this struggle are interesting.

New languages are under development by the research teams at both Yahoo and Google. Sawzall is a the topic of a research paper from Rob Pike, Sean Dorward, Robert Griesemer, and Sean Quinlan. Pig, with a much less elegant name, is an working language from Yahoo Research. Off the bat, note that Sawzall is a paper, and you can download Pig's source today. If Google has an implementation of Sawzall, they are not making it public at this time.

Both are based around respective implementations of the popular concurrency algorithm, MapReduce, originally a Google creation. Yahoo supports an open source implementation of this algorithm, named Hadoop. Google has yet and likely won't release source code or open up their MapReduce system, although much information is available through their research papers.

I guess I just find it interesting that although Google is considered so often to be the geeks company, and a more open and public loving corporate entity, much of it sometimes seems to just be face without substance. Yahoo is the one supporting the open source project, instead of a closed internal solution, and their concurrency language is available freely with its source code. Sometimes, I wonder if Yahoo is more in line with the communities than Google.

Found from Geeking with Greg.

Comments

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad. Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems. There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day. The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad. You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You u