Is anyone else disturbed by this conglomeration of power?... won't all our eggs be in one basket?
Yes, this thought occurred to me too. However, I'm less concerned with power than with the eggs-in-one-basket aspect. Open Source is about distributing control as well as effort, and I feel a little uneasy about so much Open Source work being held in one physical location and in one legal jurisdiction.
Sourceforge is superb, and so is vacuuming up hundreds of OSS projects. All those projects in one server room? Scary.
Yes sorry, that wasn't the reason. I should have checked before posting. This is the reason. An extract:
Databases, by definition, mean dealing with huge amounts of data. They also often contain very small computational requirements (although this is not always the case). This means that the bottleneck for database operations usually isn't CPU horsepower, but disk bandwidth. This means that distributed.net would be ill suited to help.
This has been discussed on several occasions at distributed.net. The stumbling block is that you would be creating a commercially valuable resource in a not-for-profit organisation. Oh yes, and issues of faking and spamming come to light when you think about it.
Slightly offtopic, but conceding to consumer demand was a Perestroika (restructuring) policy. Protecting their population from Rocky IV would rather be in opposition to Glasnost (openness).
Slashdot Mirror
Yes, this thought occurred to me too. However, I'm less concerned with power than with the eggs-in-one-basket aspect. Open Source is about distributing control as well as effort, and I feel a little uneasy about so much Open Source work being held in one physical location and in one legal jurisdiction.
Sourceforge is superb, and so is vacuuming up hundreds of OSS projects. All those projects in one server room? Scary.
Yes sorry, that wasn't the reason. I should have checked before posting. This is the reason.
An extract:
Databases, by definition, mean dealing with huge amounts of data. They also often contain very small computational requirements (although this is not always the case). This means that the bottleneck for database operations usually isn't CPU horsepower, but disk bandwidth. This means that distributed.net would be ill suited to help.
This has been discussed on several occasions at distributed.net. The stumbling block is that you would be creating a commercially valuable resource in a not-for-profit organisation. Oh yes, and issues of faking and spamming come to light when you think about it.
Slightly offtopic, but conceding to consumer demand was a Perestroika (restructuring) policy. Protecting their population from Rocky IV would rather be in opposition to Glasnost (openness).