Can Apple make a new version of the APSL, then pull the rug out from under everyone by using the APSL v1.0 section 9 under the previous license clause of the APSL? Or would that just invalidate using the code under APSL v1.0.
Yeah. I just read the APSL part 7. From what I saw it would just invalidate using the code under APSL 1.0. This would mean that after APSL 1.1 or 2.0 are created, that Apple could at anytime destroy the right to use "original" code licensed under APSL 1.0. Something that should be watched for.
It's the whole "inch, mile" thing. People who might get burned if this possibility happens will be less likely to help free software. Therefore, people such as Broce Perens want to see this fixed.
It doesn't say that. It says they may terminate YOUR right to use the software if any of the original source (ie. their *original* source code) becomes the subject of a *claim* of infringement by anyone (note they didn't mention that YOU had to make the claim) (ie. obviously this code doesn't infringe, but the GNUstep/KDE/GNOME/XXX on top of Darwin initiative(s) is taking away our (apple's) sales, so we're going to ask Joe Blow on the street corner to make a claim in court, so we can pull the license).
If they pull the source out using this clause, there will be no earlier license to keep it free under.
They are secondary beneficiaries. The primary beneficiaries are Linus and the other kernel people.
I do understand this, but I think it even odder to work on something that will be of primary benefit solely to Apple. At least with linux, someone else can make money throuugh another distribution/Support Network/etc.... The major monetary beneficiary of this work on Apple's core will be apple.
Many of his points seem kind of obvious, though it's good to shine a little light on the obvious in case you've forgot.
I'll read him, but skim as I usually do. If I want good prose, I go sci-fi/fantasy/Frost; His seems a little heavy (like an ultra-rich fudge; good initially, sickening after a while).
2) As noted in another comment, you forgot to include domain names that are less than 26 characters long.
No, the previous poster didn't. That's where the summation (my inbuilt spell checker is outta whack, I'm pretty sure that's not correct) came from. ie. 36^1 for the 1 digit +.com names, 36^2 for the two digit names, etc....
I found a page a while back with a load of chording keybds. Lost it though, try wearables.blu.org for a list of chorders. Handykey.com recently had a sale on twiddlers, I picked two up for US$294. Don't think the sale is going on anymore.
I believe more people would have respect for Christianity (especialyl Americans;) ) if they did just that.
I have read the original statement. It makes me dislike christianity/judaism/islam even more. That said, what X was in the past doesn't matter when you're dealing with what X is in the present. I respect christianity the way a schizophrenic respects their schizophrenia.
What's wrong with that? Don't/didn't you use extracurricular activities to make your college application look better? Do anything on the side to improve your resume? At least he's giving us something in return. You might not think it worth it, but I don't mind.
I do not disagree with you, but who are you to determine who is "one of our own"? Tens of thousands of people read slashdot, obviously some of them like Katz. Therefore, he is "one of our own" to a sub-section of slashdot. The owner's of the site let him on; if anyone should be allowed to determine who is "one of our own", it is them.
Is anyone coming up with a player that will support multiple codecs (perhaps through plugin modules/pcmcia slots)? This and the lack of storage are the reasons I haven't bought a rio, etc....
Slashdot Mirror
But some of these people are saying, "Hey apple, we would love to touch your code, but not unless you make some modifications to this license."
Can Apple make a new version of the APSL, then pull the rug out from under everyone by using the APSL v1.0 section 9 under the previous license clause of the APSL? Or would that just invalidate using the code under APSL v1.0.
Yeah. I just read the APSL part 7. From what I saw it would just invalidate using the code under APSL 1.0. This would mean that after APSL 1.1 or 2.0 are created, that Apple could at anytime destroy the right to use "original" code licensed under APSL 1.0. Something that should be watched for.
It's the whole "inch, mile" thing. People who might get burned if this possibility happens will be less likely to help free software. Therefore, people such as Broce Perens want to see this fixed.
It doesn't say that. It says they may terminate YOUR right to use the software if any of the original source (ie. their *original* source code) becomes the subject of a *claim* of infringement by anyone (note they didn't mention that YOU had to make the claim) (ie. obviously this code doesn't infringe, but the GNUstep/KDE/GNOME/XXX on top of Darwin initiative(s) is taking away our (apple's) sales, so we're going to ask Joe Blow on the street corner to make a claim in court, so we can pull the license).
If they pull the source out using this clause, there will be no earlier license to keep it free under.
* Where YOUR = the License reader.
Proof would be nothing more than a one-liner in the source-code. bzip2 had its license changed from .1* to .9.*. That still leaves .1* under the GPL.
No. If you don't release it (or the binary), they can't touch you.
Halloween documents anyone? If Apple wants to ensure the license is valid, it must enforce it.
They are secondary beneficiaries. The primary beneficiaries are Linus and the other kernel people.
I do understand this, but I think it even odder to work on something that will be of primary benefit solely to Apple. At least with linux, someone else can make money throuugh another distribution/Support Network/etc.... The major monetary beneficiary of this work on Apple's core will be apple.
Is it just me, or does it strike anyone else as odd that people will spend their time programming for a for-profit company for no pay?
Many of his points seem kind of obvious, though it's good to shine a little light on the obvious in case you've forgot.
I'll read him, but skim as I usually do. If I want good prose, I go sci-fi/fantasy/Frost; His seems a little heavy (like an ultra-rich fudge; good initially, sickening after a while).
2) As noted in another comment, you forgot to include domain names
.com names, 36^2 for the two digit names, etc....
that are less than 26 characters long.
No, the previous poster didn't. That's where the summation (my inbuilt spell checker is outta whack, I'm pretty sure that's not correct) came from. ie. 36^1 for the 1 digit +
Not so funny when you realize a (hopefully small) segment of the US populace doesn't have a clue where Hawaii is.
Would you then need a passport to board the lift-off vehicle and return to Earth?
I found a page a while back with a load of chording keybds. Lost it though, try wearables.blu.org for a list of chorders. Handykey.com recently had a sale on twiddlers, I picked two up for US$294. Don't think the sale is going on anymore.
>While we all know Hz aren't directly related to processing power, 1.2 GHz is not 3x faster than 800 MHz.
I have read the original statement. It makes me dislike christianity/judaism/islam even more. That said, what X was in the past doesn't matter when you're dealing with what X is in the present. I respect christianity the way a schizophrenic respects their schizophrenia.
What's wrong with that? Don't/didn't you use extracurricular activities to make your college application look better? Do anything on the side to improve your resume? At least he's giving us something in return. You might not think it worth it, but I don't mind.
I do not disagree with you, but who are you to determine who is "one of our own"? Tens of thousands of people read slashdot, obviously some of them like Katz. Therefore, he is "one of our own" to a sub-section of slashdot. The owner's of the site let him on; if anyone should be allowed to determine who is "one of our own", it is them.
Is anyone coming up with a player that will support multiple codecs (perhaps through plugin modules/pcmcia slots)? This and the lack of storage are the reasons I haven't bought a rio, etc....