I think a lot of people focusing on the licensing issue are missing something that has been brought up multiple times.
There are two different licenses at work here. The first is the EULA for the pre-compiled by Google and distributed by Google BINARY program...
The second is the BSD permissive license over the code used to actually BUILD the binaries.
There is nothing, at all, to stop somebody from vetting the code for any phone-home system calls, and ripping those out. This has already been brought up back in post #61 : http://www.hardforum.com/showpost.php?p=1032978488&postcount=61
Why add the text into the EULA? Because that's the EULA. That's for the product that Google has put together themselves. That's not the program source code. They are two separate licenses.
Technically, somebody who builds their own version of Chrome could attach any EULA they wanted to on the final product. That's what a BSD license implicitly and explicitly allows.
However, the focus on the license ignores the goal of what Chrome is.
Chrome is not an attempt at making a full fledged browser to go up against FireFox and Opera.
and no, I'm not insane.
Chrome is a technological demonstration. For those of you who pay attention to cars, it's a concept car. It's a product that shows where the industry could go. After a day with the program, Chrome is a good indication of where browsers will go.
However, all of the underlying parts of Chrome, are open-sourced. The source-code is available now completely for the Windows x86 platform, and also in portions for Linux and OSX platforms.
The idea is for other companies to take the ideas, if they like them, and use them in their products. Somebody said that FireFox is the darling of the internet just a few posts ago, and most of us would agree about that. There's nothing to stop FireFox from adopting the technology Google has developed, or developing that technology further. That is the whole point of the Chrome browser. There's nothing to stop Opera from developing from the code either.
So, if you don't like the license attached to the binary copy provided by Google, big deal. That's no reason to just dump the idea as a whole in the trash can.
There are two different licenses at work here. The first is the EULA for the pre-compiled by Google and distributed by Google BINARY program...
The second is the BSD permissive license over the code used to actually BUILD the binaries.
There is nothing, at all, to stop somebody from vetting the code for any phone-home system calls, and ripping those out. This has already been brought up back in post #61 : http://www.hardforum.com/showpost.php?p=1032978488&postcount=61
Why add the text into the EULA? Because that's the EULA. That's for the product that Google has put together themselves. That's not the program source code. They are two separate licenses.
Technically, somebody who builds their own version of Chrome could attach any EULA they wanted to on the final product. That's what a BSD license implicitly and explicitly allows.
However, the focus on the license ignores the goal of what Chrome is.
Chrome is not an attempt at making a full fledged browser to go up against FireFox and Opera.
and no, I'm not insane.
Chrome is a technological demonstration. For those of you who pay attention to cars, it's a concept car. It's a product that shows where the industry could go. After a day with the program, Chrome is a good indication of where browsers will go.
However, all of the underlying parts of Chrome, are open-sourced. The source-code is available now completely for the Windows x86 platform, and also in portions for Linux and OSX platforms.
The idea is for other companies to take the ideas, if they like them, and use them in their products. Somebody said that FireFox is the darling of the internet just a few posts ago, and most of us would agree about that. There's nothing to stop FireFox from adopting the technology Google has developed, or developing that technology further. That is the whole point of the Chrome browser. There's nothing to stop Opera from developing from the code either.
So, if you don't like the license attached to the binary copy provided by Google, big deal. That's no reason to just dump the idea as a whole in the trash can.