But that's because of the business model. AGPL is to be used when you are not bothered by competition but you don't want fragmentation of your codebase.
Remember (A)GPL is for protecting the right of the users, not of the coders. If you want to protect your rights as the provider of a software-as-a-service solution, you'd better _not_ use AGPL.
If all you want is a free ride on the work of others, stay away of the AGPL.
"For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
This is actually the first clever use of AGPL I am aware of: it prevents a competitor to form around an altered version of Launchpad. If they try, they have to give it to their users and thus Canonical.
It prevents fragmentation of the code base. Very, very clever.
And exactly how IBM not being a bunch of code-hugging hippies makes Microsoft a bunch of altruistic GPL coders that only want to make Linux a nicer operating system?
They are all GNU/Linux. You can't compare BSD to the Linux kernel, but you can compare it to the Linux kernel plus the GNU userland.
The fact there are different distros that share slightly off-sync versions of a common base continuously forking and merging back makes for a more interesting history than the, as the GP aptly described, BSD fork bloodbath.
BSD is for those who want to write free software, while GPL is for those who write free software and want it to be free forever. They may be called ideologues, but you can't question the GPL side of the fence breeds greater diversity and a richer ecosystem.
Perhaps developers who feel "idle" (if they exist at all) should be writing automated tests or, at the very least, thinking on how to automate stuff like testing for real-time kernel concurrency problems or device-driver weirdness.
"We've had decades of shuttle launches, that this is now routine."
Call it routine all you want. Watching something the size of a building lift off to space has always, is, and will continue to be an impressive technical achievement for the foreseeable future.
The shuttle is an expensive, impractical, fragile, dangerous, whatever vehicle, but it is still a remarkable machine. It may not be the best solution to place stuff in LEO, or not even a very good one, but it's beautiful and inspiring and that counts.
As for putting stuff in LEO, well... 40 years ago, we ventured into the vast ocean of space, swam a little until the island we see close to the beach and came back with wonderful stories. Since then, we have restricted ourselves to our shores, learning how to do stuff, how not to do stuff and dreaming of our future voyages. It will be a very sad day the one when we give up exploring beyond the confines of our beautiful planet.
Robots can't tell stories and none can say how it felt to watch the Earth from afar.
Seriously, I always VPN myself back to base every time I use a network I don't trust completely. If someone can break my crypto, he or she deserves my data.
Setting up a VPN is easy, quick and painless. Why not do it?
Even if all you do is accelerate all the fuel and oxidizer to Mach 2 and couple miles up, you have huge savings that can be passed along in payload capacity.
It would make for a steep rail. One would need very unpopular mountain to build it.
Slashdot Mirror
OS/2 wouldn't exist. We would be using something derived from GEM on something derived from CP/M-86 instead.
They are dumber, show poorer judgment and click more ads. Is there anything else here I haven't noticed?
I see we failed to see the "don't feed the trolls" sign...
But that's because of the business model. AGPL is to be used when you are not bothered by competition but you don't want fragmentation of your codebase.
Remember (A)GPL is for protecting the right of the users, not of the coders. If you want to protect your rights as the provider of a software-as-a-service solution, you'd better _not_ use AGPL.
If all you want is a free ride on the work of others, stay away of the AGPL.
"Radar signals can lead to small but rapid spikes of heat in the head that generate sound waves"
The head that makes sound waves as opposed to the other head... Well, you get the point...
They are not completely missing from GPLv2
from http://www.gnu.org/licenses/gpl-2.0.html, clause 7
"For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program."
This is actually the first clever use of AGPL I am aware of: it prevents a competitor to form around an altered version of Launchpad. If they try, they have to give it to their users and thus Canonical.
It prevents fragmentation of the code base. Very, very clever.
Are you trolling?
No. He just wants it under a BSD license so he can close it up, take a free ride on the work of others and make it part of his product.
"its like placing a 7 year old at the controls of a breeder reactor!"
I think a PWR reactor would be a more appropriate analogy. IIRC, breeders are not as fragile.
And exactly how IBM not being a bunch of code-hugging hippies makes Microsoft a bunch of altruistic GPL coders that only want to make Linux a nicer operating system?
It still surprises me that a country with the best restaurants and best chefs in the world.
Is there a country that doesn't claim that?
Actually, for an Atheist, it should evaluate to null. Agnostics leave it undefined.
Seems a good reason to make a couple Kindle-size "deffective by design" stickers.
They are all GNU/Linux. You can't compare BSD to the Linux kernel, but you can compare it to the Linux kernel plus the GNU userland.
The fact there are different distros that share slightly off-sync versions of a common base continuously forking and merging back makes for a more interesting history than the, as the GP aptly described, BSD fork bloodbath.
BSD is for those who want to write free software, while GPL is for those who write free software and want it to be free forever. They may be called ideologues, but you can't question the GPL side of the fence breeds greater diversity and a richer ecosystem.
Don't you have a release to do, Theo?
If there is a human testing, it's already wrong.
Perhaps developers who feel "idle" (if they exist at all) should be writing automated tests or, at the very least, thinking on how to automate stuff like testing for real-time kernel concurrency problems or device-driver weirdness.
Nothing compares to the sensation of being there. You can *feel* the immense power required to lift that huge piece of machinery up to space.
I saw it once as a kid. I will never forget. I won't say that made me an engineer, as I joke this is an innate condition, but it certainly helped.
"We've had decades of shuttle launches, that this is now routine."
Call it routine all you want. Watching something the size of a building lift off to space has always, is, and will continue to be an impressive technical achievement for the foreseeable future.
The shuttle is an expensive, impractical, fragile, dangerous, whatever vehicle, but it is still a remarkable machine. It may not be the best solution to place stuff in LEO, or not even a very good one, but it's beautiful and inspiring and that counts.
As for putting stuff in LEO, well... 40 years ago, we ventured into the vast ocean of space, swam a little until the island we see close to the beach and came back with wonderful stories. Since then, we have restricted ourselves to our shores, learning how to do stuff, how not to do stuff and dreaming of our future voyages. It will be a very sad day the one when we give up exploring beyond the confines of our beautiful planet.
Robots can't tell stories and none can say how it felt to watch the Earth from afar.
One could also use "Please, God, don't let them screw up"
Seriously, I always VPN myself back to base every time I use a network I don't trust completely. If someone can break my crypto, he or she deserves my data.
Setting up a VPN is easy, quick and painless. Why not do it?
Even if all you do is accelerate all the fuel and oxidizer to Mach 2 and couple miles up, you have huge savings that can be passed along in payload capacity.
It would make for a steep rail. One would need very unpopular mountain to build it.
Instead of Russia?
"nor can you use the search function"
That's really bad if you want to keep a library in your backpack. Indexing and search should be the first thing to be implemented after rendering.
GCC _is_ good enough for a lot of stuff.
I would consider other compiler if it can compile all of my current distro to all architectures it supports. I find the x86 world remarkably boring,
They also have an easier job. MSVC doesn't need to address as many architectures as GCC does. IIRC, there is no MSVC for s/390