Pressure of the writing is an indicator of the person's stress level.
Nah, it's just because they're making six copies. The pink copy goes to accounting, the canary copy to HR, the green copy to the manager, the... you get the idea.
OTOH, that can be stressful.
A person who tends to come back and write back over the top of their words (not to make a correction -- writing over it twice or more) is a sign of dishonesty.
More likely a sign that their pen was skipping, and that it's probably time they got a new one.
Your signature tells how you want people to think you are.
My signature looks like an EKG trace. Does that mean I want people to think I have heart?
Oh, I've picked on plenty of other languages too. It's just that I don't think any other that I've used has led me to the level of cursing that FORTRAN has.
Oh, except maybe COBOL.
(For my sins, I've had to maintain tens of thousands of lines of other people's FORTRAN code at various points in my career, including early versions of SPICE, which inserted machine code into an array and then passed execution to it! OTOH, "Collosal Cave" wasn't bad.)
Original source, nope. So it may well be an urban legend, but there are additional details: The spacecraft was an early Venus probe. The loss was because the launch was sufficiently off course that the Range Safety Officer called an abort, and blew it up.
You left out whitespace being meaningless and implicit declaration of variables -- which can lead to things like
DO 10 I = 1.10
unexpectedly assigning 1.10 to the new variable DO10I instead of starting a do-loop with I as the loop variable, ranging from 1 to 10. (Which, for the non FORTRAN cogniscenti, would be
DO 10 I = 1,10
where the first 10 is the label of the end of the loop)
Which led to the loss of a space probe, back in the day.
Problem is that most packages these days drag a ton and a half of baggage around with them, and it's harder to install just the stuff you need than just throw everything in. (I'm not likely to ever need Swahili or Urdu language support, but there it is...)
Further, Roman numerals were simply a notation system for describing abacus tallies. It generally sucks to do math with Roman numerals unless you're doing it on an abacus, where it makes perfect sense. (The upper row, above the bar, on an abacus stands for fives, the lower rows for units (or 50 and tens, 500 and hundreds, etc.)
Yes and no. The copyright part of the license gives permission to make derivatives of Open Solaris. The patent part only gives permission to use the patents in Open Solaris, or portions thereof -- not modified or derivative works.
if your Open Source project doesn't use their code you don't have a license to use these patents.
I don't think it's even that generous. I certainly wouldn't bet that way.
or implemented in CDDL licence code that you modify or write.
Nope. Read 2.1(b) -- the Patent license is only granted to use or sale of the Original Code, not modifications thereof or of anything else licensed under the CDDL.
They are not licensing the patents for anything except the code they themselves provide, and only then if you don't modify it.
There is no explicit patent license. All Sun is saying is that they won't sue you for patent infringement over any of their patents that may be embodied in the CDDL'd Solaris code that they're promising to give out Real Soon Now.
Mighty generous of them -- that's the same sort of implicit license-to-use granted to anyone who uses code that Sun provided to them. I wouldn't expect them to sue me for patent infringment over using a (legally obtained) copy of Solaris.
Reading the fine print, this promise seems to go out the window if you modify the code in any way. This is far, far different from IBM's explicit license to use their specified patents in any way you choose, so long as the implementation is open source.
CDDL is file-based; that means that files licensed under the CDDL can be combined with files licensed under other licenses,
In that context, the only sensible meaning of "combined with" is in the sense of "aggregated with" -- i.e., you can include CDDL and non-CDDL files on the same disc.
That might be useful for files in a scripting language, which aren't compiled into an executable. However, for compilable language files, you have to create a derivative work (the object file(s)), and the resulting executable file has to satisfy the licenses of all the files from which it derives.
The CDDL won't let you create derivatives with multiple licenses, therefore you cannot usefully combine (in the compilation sense) CDDL files with other-licensed files.
I'm still scratching my head wondering how he was able to reach my connection from across the street
Directional antenna, perhaps.
If I find out it happened again I'm going to have to start pounding on his door or report him.
Nah, just bypass the interlock and aim your microwave oven at his house. That ought to take care of the directional antenna and everything attached to it.
(I shouldn't have to say this, but the above was a joke!. Aiming a microwave oven at anyone is dangerous, and besides will probably void the warranty.)
Less than seven million. I hardly think that giving out less than $2 million would bankrupt the country. And of course, most of those patents have expired.
If the gov't really wanted to abolish copyrights and/or patents (unlikely in the extreme), I think the "without just compensation" clause could be met by simply refunding the application fees. Beyond that, the gov't is simply "taking" back what they granted in the first place: a promise to use govt force if necessary to ensure the author's/inventor's temporary monopoly. That's not exactly "private property", and is why the term "intellectual property" is oxymoronic on its face.
For that matter, you haven't studied the Air Regs very well. They require -- and I'm speaking the CARs here -- parchutes for aerobatic training. (Of course Canada doesn't consider spin training "aerobatic", unlike some places.)
> Gliders are the safest planes there are
Personally I like the option of applying power and going around if something unexpected turns up on final. It's a lot easier to, in flight, convert a powered plane into a glider (with, admittedly, a crappy glide ratio) than vice versa.
Slashdot Mirror
...Windows XP, no proprietary drivers required.
Uh, what is Windows XP but one big proprietary driver?
Hey, the internet was designed to withstand a nuclear attack, remember?
(No, not really, just the loss of a few nodes.)
That first link has to be one of the funniest things I've ever read. It is a parody, right?
Wow. That adds a whole new meaning to the term "laser printer".
I want one.
Pressure of the writing is an indicator of the person's stress level.
... you get the idea.
Nah, it's just because they're making six copies. The pink copy goes to accounting, the canary copy to HR, the green copy to the manager, the
OTOH, that can be stressful.
A person who tends to come back and write back over the top of their words (not to make a correction -- writing over it twice or more) is a sign of dishonesty.
More likely a sign that their pen was skipping, and that it's probably time they got a new one.
Your signature tells how you want people to think you are.
My signature looks like an EKG trace. Does that mean I want people to think I have heart?
Oh, I've picked on plenty of other languages too. It's just that I don't think any other that I've used has led me to the level of cursing that FORTRAN has.
Oh, except maybe COBOL.
(For my sins, I've had to maintain tens of thousands of lines of other people's FORTRAN code at various points in my career, including early versions of SPICE, which inserted machine code into an array and then passed execution to it! OTOH, "Collosal Cave" wasn't bad.)
Original source, nope. So it may well be an urban legend, but there are additional details: The spacecraft was an early Venus probe. The loss was because the launch was sufficiently off course that the Range Safety Officer called an abort, and blew it up.
Which led to the loss of a space probe, back in the day.
OK, I was half kidding on that post.
Problem is that most packages these days drag a ton and a half of baggage around with them, and it's harder to install just the stuff you need than just throw everything in. (I'm not likely to ever need Swahili or Urdu language support, but there it is...)
Buy more RAM. At least to 256M, more is better. (Alas, prices are going up for old style RAM. I'm guessing yours uses what, PC-133?)
Current graphic desktops eat RAM for breakfast, lunch and dinner. (And no, swap space just doesn't do it unless you like waiting.)
Why does a office suite on a Linux box have to take up a gig of disk?!
Um, because disk only costs about fifty cents a gig these days? (OK, there's a certain minimum order...)
I meant to add:
So, given the above, the new Intel trademark stands for a chip that's about as good as a broken abacus.
Further, Roman numerals were simply a notation system for describing abacus tallies. It generally sucks to do math with Roman numerals unless you're doing it on an abacus, where it makes perfect sense.
(The upper row, above the bar, on an abacus stands for fives, the lower rows for units (or 50 and tens, 500 and hundreds, etc.)
Theoretically the resellers can in turn sue Intel for the damages they had to pay (and then some).
Don't know if it'll happen in this case, probably be settled quietly with Intel offering some discounts on future sales.
Yes and no. The copyright part of the license gives permission to make derivatives of Open Solaris. The patent part only gives permission to use the patents in Open Solaris, or portions thereof -- not modified or derivative works.
if your Open Source project doesn't use their code you don't have a license to use these patents.
I don't think it's even that generous. I certainly wouldn't bet that way.
So far IBM is winning, and Sun hasn't even entered the race. Sun hasn't freed any patents.
Sure, they'll let you use their patents in OpenSolaris, but then, Sun already lets you use their patents in Solaris. Read the fine print.
or implemented in CDDL licence code that you modify or write.
Nope. Read 2.1(b) -- the Patent license is only granted to use or sale of the Original Code, not modifications thereof or of anything else licensed under the CDDL.
They are not licensing the patents for anything except the code they themselves provide, and only then if you don't modify it.
There is no explicit patent license. All Sun is saying is that they won't sue you for patent infringement over any of their patents that may be embodied in the CDDL'd Solaris code that they're promising to give out Real Soon Now.
Mighty generous of them -- that's the same sort of implicit license-to-use granted to anyone who uses code that Sun provided to them. I wouldn't expect them to sue me for patent infringment over using a (legally obtained) copy of Solaris.
Reading the fine print, this promise seems to go out the window if you modify the code in any way. This is far, far different from IBM's explicit license to use their specified patents in any way you choose, so long as the implementation is open source.
CDDL is file-based; that means that files licensed under the CDDL can be combined with files licensed under other licenses,
In that context, the only sensible meaning of "combined with" is in the sense of "aggregated with" -- i.e., you can include CDDL and non-CDDL files on the same disc.
That might be useful for files in a scripting language, which aren't compiled into an executable. However, for compilable language files, you have to create a derivative work (the object file(s)), and the resulting executable file has to satisfy the licenses of all the files from which it derives.
The CDDL won't let you create derivatives with multiple licenses, therefore you cannot usefully combine (in the compilation sense) CDDL files with other-licensed files.
It will remain to be seen if people will accept carrying volatile fluids around with them,
What, you mean like in cigarette lighters? No, it'll never happen.
I'm still scratching my head wondering how he was able to reach my connection from across the street
Directional antenna, perhaps.
If I find out it happened again I'm going to have to start pounding on his door or report him.
Nah, just bypass the interlock and aim your microwave oven at his house. That ought to take care of the directional antenna and everything attached to it.
(I shouldn't have to say this, but the above was a joke!. Aiming a microwave oven at anyone is dangerous, and besides will probably void the warranty.)
Yes, there's a Vancouver in Washington. Southern Washington, across the river from Portland, Oregon.
Newsflash: there's also a really big island off the BC coast with that name.
Less than seven million. I hardly think that giving out less than $2 million would bankrupt the country. And of course, most of those patents have expired.
If the gov't really wanted to abolish copyrights and/or patents (unlikely in the extreme), I think the "without just compensation" clause could be met by simply refunding the application fees. Beyond that, the gov't is simply "taking" back what they granted in the first place: a promise to use govt force if necessary to ensure the author's/inventor's temporary monopoly. That's not exactly "private property", and is why the term "intellectual property" is oxymoronic on its face.
Never flown aerobatic, have you?
For that matter, you haven't studied the Air Regs very well. They require -- and I'm speaking the CARs here -- parchutes for aerobatic training. (Of course Canada doesn't consider spin training "aerobatic", unlike some places.)
> Gliders are the safest planes there are
Personally I like the option of applying power and going around if something unexpected turns up on final. It's a lot easier to, in flight, convert a powered plane into a glider (with, admittedly, a crappy glide ratio) than vice versa.