Bingo! You're right. My question is, are the others unable to interpret the plain language that says this, or are they deliberately misrepresenting it?
Both the new XFree86 clause and the original BSD clause are simple vanity clauses. Fixating on these as "restrictions" sounds pretty foolish to me. Can it possibly be that the GPL is foolishly crafted to go to war with such simple requirements, which have absolutely no bearing on whether the end product is either free beer or free speech?
"in a manned mission, the landing would be by parachute with retro rockets to slow acceleration to 0 on the surface, because the trained pilot has that ability. currently, programs don't have that ability..."
I was tempted to assume from the beginning of this thread that you were being ironic, but the text reveals no trace of ironic intent, so I'll take this at face value.
In a word, sheesh! This is exactly what computers are good at. It is nothing more esoteric than ordinary feedback control systems. I have no doubt a single PIC micro could do the job with its figurative eyes closed.
I mean, I'm in favor of manned spaceflight, but this is a totally bogus consideration.
"Bubble memory is here and... in use today... [in] Specalist machines. I suggest you do research."
Beg pardon for not taking several hours off to do research before posting:-) Actually, if you hit Webopedia http://www.webopedia.com/TERM/b/bubble_memory.html, you will see "It was once widely believed that bubble memory would become one of the leading memory technologies, but these promises have not been fulfilled."
Seriously, I hope it's fairly clear from the context that vaporware refers to stuff that never fulfilled its glowing promise; not necessarily stuff that never sold even a few units.
"What percentage of your games/music CD's from say 6 years ago isn't scratched?"
Er, 0%. Maybe I'm atypical. I agree it's a moronic, crappy design, though. Should be a cartridge. Lord knows there is plenty of profit margin in CDs and software to pay a few cents extra per disc to have it in a cartridge a la DVD-RAM.
Out of curiosity, how many of your scratched discs won't play any more?
I happen to agree we put up with WAY too much, and put off dealing with it for WAY too long (you get one brownie point for correctly discerning that the US is not perfect), but you know what? We would be blabbing about maybe doing something DECADES from now if we listened to the French, Germans, and Russians.
> The excuse that far too many automobile drivers use in the US is "I didn't see him", which > clearly shows that the driver was distracted or "filtering out" everything that wasn't an > automobile.
The excuse that far too many automobile drivers use in the US is "I didn't see him", which clearly shows that the driver was distracted or "filtering out" everything that wasn't an automobile.
Or, duh, just maybe, duh, it shows that it is harder to see a guy on a motorcycle than it is to see a car.
my question is why he made his own stack object. i could have sworn the STL has a stack object included.
Er, just a guess, but maybe the original concept of his code predated the wide availability of STL. Or quite likely, as a tutorial, he just wanted to depend on nothing beyond iostreams.
I'm more concerned with some other points:
Why "#define STYPE int" instead of "typedef int stype"?
Why the #defines for EMPTY, FULL, and PUSH_OK instead of an enum?
Why the "Stack::Stack(void)" instead of just "Stack::Stack()" (the former is a C anachronism)?
Then, of course, to get really nitpicky, he doesn't need his destructor at all (one will be generated by the compiler).
The unit symbol for kilometers/hour is km/h... K is Kelvin, P is not a unit, H is Henry. KPH would be "kilo-Henry times whatever P would be"
Exactly, but as an old geezer it does seem to me that the fad (sorry, solemn official standard) of abbreviation) has changed at some point. I seem to recall that back in my day all the multiplier prefixes above unity were capitalized, and all those below unity were lower case.
Most especially, Kilo was capitalized - and indeed, kilobytes per second is still properly written Kbps, not kbps, isn't it?
These days it would appear that all the above-unity multiplier prefixes higher than kilo are still capitalized, while kilo, hecto, and deka are not. All the below-unity ones are still lower case.
Is this true, and if so, why on earth was this change made? It is so offensive to common sense of order.
Maybe kilo is lower case to differentiate from Kelvin, and hecto from Henry, but what about deka?
You first. You could start by not reproducing, and killing yourself, because you're using stuff up. The basic problem here is that there are TOO DAMN MANY PEOPLE. Stop sweating the small stuff and address the underlying problem.
Not saving the planet is letting lots of species die out - faster than evolution can replace them.
"Lots" is kind of vague, but I don't have a knee jerk reaction to "letting" species die out. I don't think we're better off with tsetse flies than without them. I don't think the cities and suburbs are better off allowing coyotes to repopulate and kill off all the domestic cats. Do you think it's a good idea having venomous snakes in those woods you want your grandkids to enjoy walking through? Do you have a problem with dinosaurs being gone?
So because a few Canadians say 'aboot', you assume we all do.
No, didn't say that. I assume a lot of Canadians, when they say 'about', will say 'environ'. Quebecois*, dont'cha know:-)
Not that I have a problem with that. A lot of Americans will say 'en cuanto a' for 'about'. Hey, just because the Tower of Babel didn't work the first time doesn't mean we shouldn't keep trying:-)
* Please forgive the failure to render the accents. I would say "accents are so gay", but someone might be offended.
When we [Canadians] say 'about' they hear aboot, because they are used to the oo sound being an ugh sound.
WTF are you talking about? Ugh is a complete word with a vowel sound and a consonant sound. It's what the stereotyped Indian says in the old western movie. Oo is an isolated vowel sound.
We hear aboot because you say aboot. The ou in about should be pronounced like the ow in "Ow! I hurt myself!"
It could say "The gostak distims the doshes; OK?" and they would click Yes. Hell, *I* would click Yes. Life is too short to figure everything out all the time. Because it's not a dialog in isolation. It's part of your life. You've been tussling with this program for hours. You need to take a leak. It's time to mow the lawn and pay the bills. You're hungry. Your girlfriend just came into the room in a red lace teddy.
Oh, I think maybe a chem or bio attack or just a sniping or suicide bomb in his neighborhood, that can be pulled off for almost no expense, just miiiiight convince him. We may have bankrupted the USSR before we bankrupted ourselves, but I don't see us bankrupting the terrorists.
Slashdot Mirror
Bingo! You're right. My question is, are the others unable to interpret the plain language that says this, or are they deliberately misrepresenting it?
Both the new XFree86 clause and the original BSD clause are simple vanity clauses. Fixating on these as "restrictions" sounds pretty foolish to me. Can it possibly be that the GPL is foolishly crafted to go to war with such simple requirements, which have absolutely no bearing on whether the end product is either free beer or free speech?
"Why is the new liscence being rejected?"
From an exhaustive reading of the previous thread on this issue, well, er, because GPL zealots are throwing a hissy fit tantrum over nothing.
"So is it actual *SILVER* (S)"
Silver is Ag, not S.
S is sulphur.
"Silver is the best conductor ... Gold is the next best conductor, AFAIK, and doesn't tarnish."
No, actually silver is #1, copper is #2, and gold is #3.
Silver 430 W/m/K
Copper 400 W/m/K
Gold 320 W/m/K
Aluminum 235 W/m/K
"I thought copper had a lower thermal conductivity compared to silver."
Somewhat lower, but not much lower.
Silver 430 W/m/K
Copper 400 W/m/K
"no acutally gold has the highest electrical and thermal conductivity of all metals. that is why it is used in microchips"
Please, someone tell me what is the point of blabbing misinformaton about things of which you are utterly ignorant?
Silver has far higher thermal conductivity than gold.
Gold, 320 W/m/K
Silver 430 W/m/K
To the extent gold is used in microchips, it is for other reasons.
"in a manned mission, the landing would be by parachute with retro rockets to slow acceleration to 0 on the surface, because the trained pilot has that ability. currently, programs don't have that ability ..."
I was tempted to assume from the beginning of this thread that you were being ironic, but the text reveals no trace of ironic intent, so I'll take this at face value.
In a word, sheesh! This is exactly what computers are good at. It is nothing more esoteric than ordinary feedback control systems. I have no doubt a single PIC micro could do the job with its figurative eyes closed.
I mean, I'm in favor of manned spaceflight, but this is a totally bogus consideration.
"Bubble memory is here and ... in use today... [in] Specalist machines. I suggest you do research."
:-) Actually, if you hit Webopedia http://www.webopedia.com/TERM/b/bubble_memory.html , you will see "It was once widely believed that bubble memory would become one of the leading memory technologies, but these promises have not been fulfilled."
Beg pardon for not taking several hours off to do research before posting
Seriously, I hope it's fairly clear from the context that vaporware refers to stuff that never fulfilled its glowing promise; not necessarily stuff that never sold even a few units.
"Hi[s] computer can play them[,] can[']t [it] [...] DUH."
Mr. ill-mannered Coward - easy on the caffeine this morning.
Few PCs other than high end units have more than one 5-1/4" bay any more. Also, you are assuming he HAS a PC that is equipped to output video to a TV.
Points 1 and 3 still apply in this scenario.
"What percentage of your games/music CD's from say 6 years ago isn't scratched?"
Er, 0%. Maybe I'm atypical. I agree it's a moronic, crappy design, though. Should be a cartridge. Lord knows there is plenty of profit margin in CDs and software to pay a few cents extra per disc to have it in a cartridge a la DVD-RAM.
Out of curiosity, how many of your scratched discs won't play any more?
Same thing that happened to mountains of other vaporware. Bubble memory, digital paper, holographic storage, carbon nanotubes, etc, etc, etc.
"Your[e] OLD player will still work." [Flames deleted]
My first thought was similar to this, but I quickly thought better of it.
1) Maybe he could sell his old player on ebay and reduce his investment if only the new player is compatible.
2) Not everyone has the room to keep two players in service.
3) The old player will crap out at some point. The point is that he will have to maintain two players in service.
looks like you woke up a bit late to save them
BWAAA HAAAA HAAAAA !!!
I happen to agree we put up with WAY too much, and put off dealing with it for WAY too long (you get one brownie point for correctly discerning that the US is not perfect), but you know what? We would be blabbing about maybe doing something DECADES from now if we listened to the French, Germans, and Russians.
> The excuse that far too many automobile drivers use in the US is "I didn't see him", which
> clearly shows that the driver was distracted or "filtering out" everything that wasn't an
> automobile.
Or lying.
Or, duh, telling the simple truth.
The excuse that far too many automobile drivers use in the US is "I didn't see him", which clearly shows that the driver was distracted or "filtering out" everything that wasn't an automobile.
Or, duh, just maybe, duh, it shows that it is harder to see a guy on a motorcycle than it is to see a car.
my question is why he made his own stack object. i could have sworn the STL has a stack object included.
Er, just a guess, but maybe the original concept of his code predated the wide availability of STL. Or quite likely, as a tutorial, he just wanted to depend on nothing beyond iostreams.
I'm more concerned with some other points:
Why "#define STYPE int" instead of "typedef int stype"?
Why the #defines for EMPTY, FULL, and PUSH_OK instead of an enum?
Why the "Stack::Stack(void)" instead of just "Stack::Stack()" (the former is a C anachronism)?
Then, of course, to get really nitpicky, he doesn't need his destructor at all (one will be generated by the compiler).
Wouldn't it be great if there was a LAW requiring hardware manufacturers to release hardware specifications and/or source code?
How about just a law requiring people to be NICE?
That would cover your wish, plus a whole lot of others, in one simple stroke.
The unit symbol for kilometers/hour is km/h... K is Kelvin, P is not a unit, H is Henry. KPH would be "kilo-Henry times whatever P would be"
Exactly, but as an old geezer it does seem to me that the fad (sorry, solemn official standard) of abbreviation) has changed at some point. I seem to recall that back in my day all the multiplier prefixes above unity were capitalized, and all those below unity were lower case.
Most especially, Kilo was capitalized - and indeed, kilobytes per second is still properly written Kbps, not kbps, isn't it?
These days it would appear that all the above-unity multiplier prefixes higher than kilo are still capitalized, while kilo, hecto, and deka are not. All the below-unity ones are still lower case.
Is this true, and if so, why on earth was this change made? It is so offensive to common sense of order.
Maybe kilo is lower case to differentiate from Kelvin, and hecto from Henry, but what about deka?
Save the planet means .. keep it all the same ...
You lose. Nothing stays the same.
So help save the planet and be a hero!
You first. You could start by not reproducing, and killing yourself, because you're using stuff up. The basic problem here is that there are TOO DAMN MANY PEOPLE. Stop sweating the small stuff and address the underlying problem.
Not saving the planet is letting lots of species die out - faster than evolution can replace them.
"Lots" is kind of vague, but I don't have a knee jerk reaction to "letting" species die out. I don't think we're better off with tsetse flies than without them. I don't think the cities and suburbs are better off allowing coyotes to repopulate and kill off all the domestic cats. Do you think it's a good idea having venomous snakes in those woods you want your grandkids to enjoy walking through? Do you have a problem with dinosaurs being gone?
That's why it's called Slashdot. If it doesn't appeal, why not try ForwardSlash DotExe instead??
Hmmm, maybe because Slashdot is forward slash - Windows uses backslash.
I mean how hard is it to know the difference between forward slash (AKA just slash) and backslash.
So because a few Canadians say 'aboot', you assume we all do.
:-)
:-)
No, didn't say that. I assume a lot of Canadians, when they say 'about', will say 'environ'. Quebecois*, dont'cha know
Not that I have a problem with that. A lot of Americans will say 'en cuanto a' for 'about'. Hey, just because the Tower of Babel didn't work the first time doesn't mean we shouldn't keep trying
* Please forgive the failure to render the accents. I would say "accents are so gay", but someone might be offended.
When we [Canadians] say 'about' they hear aboot, because they are used to the oo sound being an ugh sound.
WTF are you talking about? Ugh is a complete word with a vowel sound and a consonant sound. It's what the stereotyped Indian says in the old western movie. Oo is an isolated vowel sound.
We hear aboot because you say aboot. The ou in about should be pronounced like the ow in "Ow! I hurt myself!"
It could say "The gostak distims the doshes; OK?" and they would click Yes. Hell, *I* would click Yes. Life is too short to figure everything out all the time. Because it's not a dialog in isolation. It's part of your life. You've been tussling with this program for hours. You need to take a leak. It's time to mow the lawn and pay the bills. You're hungry. Your girlfriend just came into the room in a red lace teddy.
Oh, I think maybe a chem or bio attack or just a sniping or suicide bomb in his neighborhood, that can be pulled off for almost no expense, just miiiiight convince him. We may have bankrupted the USSR before we bankrupted ourselves, but I don't see us bankrupting the terrorists.