How Microsoft Learned to Stop Worrying and (Almost) Love Open Source
1 comments Posted by Paul Lenser at 5:23 PM
Here's a good example of tinkering a program's code to help do your job more effectively. Unfortunately, Microsoft's Kinect is not open sourced and therefore must be hacked in order to edit the code.
"Hacking Microsoft’s Kinect seems to be a worldwide fad right now, but this latest repurposing might be the most practical ever. A group of graduate engineering students at the University of Washington have hacked a Kinect so it can help doctors perform surgery.
University of Washington’s newspaper, The Daily, details the students' work, which involved writing new code for Microsoft’s Kinect that allowed it to interface with their robotic equipment and basically send feedback about a patient’s body position back through the system. Because of this tracking, the students were able to workout where important internal organs were and prevent the machines from cutting too deep.
“We could define basically a force field around, say, a liver,” said Howard Chizeck, University of Washington’s professor of electrical engineering. “If the surgeon got too close, he would run into that force field and it would protect the object he didn’t want to cut.”
What is ethical when it comes to tinkering with patent protected Hardware?
3 comments Posted by Sam at 10:39 AM
What is ethical when it comes to tinkering with patent protected hardware? Is it different for hardware than it is for software? This article introduces Adafruit which is a company that sells DIY electronic kits and open source software. They are searching for programmers capable of hacking the new Microsoft Kinect device. Adafruit is offering a $2,000 reward to programmers that can produce drivers that will unlock the devices RGB camera, a depth-sensor, four microphones and motorized pivot. Microsoft is not supporting their efforts to unlock the device and has mentioned the possibility of a lawsuit. The situation is similar to the launch of Linux, but on a much smaller scale. Software giant Microsoft is trying to control the uses of its product, but creative programmers see potential for more functionality.
Microsoft fosters a containment culture. I think that if Microsoft allowed their customers to modify their hardware products they would see growth in sales. They need to capitalize on the modifications that their users are going to make regardless of their support.
I read an article yesterday about an undercover officer who videotaped a college student modifying an Xbox 360. The student was charging $60 for a modification on the Xbox that would allow you to download old school games to the hard drive. He is facing up to 10 years in prison. I think that something is very wrong with our laws if they are going to sentence a creative college student to 10 years in prison for making the Xbox better than it was.
http://hbswk.hbs.edu/item/4834.html
I came across this article and thought that it would be extremely helpful for those people who are writing their Case Report about the Linux case. It's very relevant to our course material for this week.
Basically, the article highlights the benefits of both Microsoft and Linux-type software. The authors conclude that it is unlikely that one of the systems will force the other one out. However, they explore the different situations that could arise that could potentially make this happen.
Parts of the article get a little detailed and hard to follow, but for the most part it is very informative. The most interesting part to me was the section that discusses how Microsoft could benefit from piracy when that piracy is from people who would not buy Microsoft to begin with. This is because Microsoft is not losing sales to them, yet they are still increasing the value of the system and moving users away from Linux.
Anyway, hope you enjoy because I did!
