For our family car, a 2006 Mercedes-Benz C-class station wagon, I wanted to be able to connect a MP3 player to the car audio system. We have an iPod and the girls have some other MP3 players as well. Although the CD player in the car can play MP3 CDs, it doesn’t always work. It seems to depend on the manufacturer of the blanks as well as the software the MP3 CD has been recorded with.
The Google Web Toolkit team has announced Google Web Toolkit Version 1.3 Release Candidate on the Google Web Toolkit Blog and the Official Google Blog. There have been no code changes since GWT Version 1.2, but all of the source code for GWT has been released under the Apache 2.0 license. This means that the core Java-to-JavaScript compiler and the hosted mode debugger are now available under the same Apache 2.0 license. Previously, only the user libraries were published under that license.
Linux continues to penetrate their markets. Other Open Source projects do it on the Windows platform as well. It’s not the current situation but the trend that worries them. And they don’t seem to have a working strategy against it. Immediately after the recent Novell/Microsoft deal, that included a patent covenant, Steve Ballmer said something like: “We’ve had an issue, a problem that we’ve had to confront, which is because of the way the GNU General Public License works, and because Open Source Linux does not come from a company - Linux comes from the community - the fact that that product uses our patented intellectual property is a problem for our shareholders”. So, Linux infringes upon Microsoft’s IP? Tell the community where Linux does this. If it really does, they would like to fix it. It sounds so much like what SCO tried. First, there were “millions of lines of code” that were infringing, now it’s down to zero lines. If Microsoft can’t learn from the mistakes of others, it has to repeat them. But because of how the US patent system works, they probably can put other companies out of business who refuse to cooperate simply by sueing them. Their claims don’t have to have a solid base. They don’t have it right now.
There’s an interesting article on how to overcome the same origin policy used by modern web browsers. It’s a security policy that prevents JavaScript from accessing a location different from the one it was loaded from. Same location normally means same protocol, subdomain, and domain. The same origin policy is sometimes called same site policy. One of the reasons for having this policy is to fix security issues like cross site scripting.
