The other thing that a lot of people who argue this point seem to miss is that the Jedi do die out in the end! I mean, it is a parallel to what happened in real life to the knights on this planet, and purposely so. It's the end of chivalry in Star Wars just as it was here, and it happens in Star Wars for some of the very same reasons.
"Help me, Obi-don Quixote. You're my only hope!"
(ahem)
Okay, my two cents on light sabers -- a few years ago I read another article that talked about how Star Wars tech might, maybe, perhaps work. The author consulted some physicists blah blah blah and suggested that the term light saber is intended to be descriptive by appearance but not by mechanism -- that a plasma controlled by a very powerful electromagnet could be made to appear not unlike the blade of a light saber -- the "blade" would actually be a tight loop, but you really couldn't notice the difference in the glow. Of course, it'd take more than a couple of "D" cells to power the thing...
I concur. While I may disagree with their presumed motivations, I like that the proposed definition describes the *process* of science -- which I agree is what science is all about, the process of creating knowledge.
Of course (TANGENT ALERT!), the remaining reference to "natural phenomena" still precludes even the question "is computer science a science?"
Hmm... I could scrap my cable modem and set up a Yagi pointing toward downtown Dayton. You think 20 or so elements would get me enough gain from Xenia?
In "Where No Man Has Gone Before" and "The Cage", the women wore pants, not miniskirts. It stands to reason that when Kirk, Spock, and McCoy were cadets, the skirts weren't the uniform of the day.
Something else that I noticed (hmm... maybe this is something for which I could prepare a grant request to study...) -- back when I was working on my master's thesis, I noticed one of the other guys in the lab was two-finger typing -- just two index fingers curved at 90' angles. Naturally, I teased him about it. The thing of it is, you really couldn't call it hunt-and-peck, since he "knew" exactly where the keys were. All the motion was at the elbows and (to a lesser degree) the shoulders. He was probably going at a good 40-50 wpm, which is certainly slower than I can touch-type, but he never once rubbed his knuckles or wrists.
No sweat. Your mistake was assuming the accuracy of CNN;D.
This, the same CNN that during the 1997 northern plains flooding, expressed concern that "now that Grand Forks (North Dakota) has suffered, the residents of Fargo are nervous", until apparently someone pointed out that Fargo had been flooded a couple days previous, that Fargo was upriver from Grand Forks. So then the map showed Fargo located north of Grand Forks (after all, we all know rivers flow down on the map). More blatantly was about a year before (but I don't remember the news story) when they showed North Dakota labeled "South Dakota" and vice-versa. Whoda thunk that South Dakota was actually north of North Dakota!? cb
CNN Witnesses said the object appeared to be traveling from southeast to northwest, "which means it was heading inland," Baalke said.
fjordboy At about 6:30 EST this evening, many meteors broke apart and headed south coming from Canada.
Someone's confused. cb
I am not dismissing the value of this work, but so long as developer & maintainer time is more valuable than processor time, when you choose a language, you should consider how well each language will make the developers' and (especially) the maintainers' jobs easier.
An example of how this can be considered is found in the appendices of "A Gentle Introduction to Software Engineering" (2,565 KB; MS Word format) by the Air Force's Software Technology Support Center (STSC). The appendices come from a document written in March 1996, so it's a little dated (predates the C++ standard, does not address Java, Python, or Perl), but the idea is there. (I like that it keeps repeating "Bad programmers can write bad code in any language, but a good language facilitates the production of good code by good programmers.".)
Including the performance achievable with each language is already in the formulation offered by STSC. The obvious caveat is that you look at the performance of benchmarks related to your application.
The "tubes" appear to be an optical illusion. Look especially in "Tubes 1". Look at the shadows on the crater in the upper right, then look at the shadows in the "tube". It appears to be a valley, not a tube. The "tiger-stripe" ridging is the result of the cliff edge slumping. Likewise, the "track" is a slumped cliff edge. The triangles are shadows in a dune field. cb
See
a
lawyer
At a minimum, I expect the only way to avoid a conflict of interest is to recuse yourself from this project for your company. Even still, this may not be enough, since what you're working on at home is, by your description, something your employer would want to market. cb
I think a couple issues need to be clarified. As a general rule, when the government contracts out for original software development, the copyright is held by the contractor (or whomever the contractor may assign it to). When the government hires an employee to develop software, then the government "owns" it, in the sense that the employee cannot claim copyright on it. By law, however, with rare exception (such as government-owned academic institutions), works developed by the government are not copyrighted.
If your employer, the contractor, believes it owns the copyright, that's between you and your employer. If, for some reason, DoD has a legitimate claim of ownership, then it's public domain.
Incidentally, the third option -- a government employee developing software while off-duty, using only his/her own equipment, and not as part of his/her official duties -- then the employee keeps the copyright, but the government will insist on a no-cost license for government use. cb
Slashdot Mirror
Personally, I think a good definition of a major planet is one that is massive enough that, given its composition, it assumes a sphere-like shape.
The other thing that a lot of people who argue this point seem to miss is that the Jedi do die out in the end! I mean, it is a parallel to what happened in real life to the knights on this planet, and purposely so. It's the end of chivalry in Star Wars just as it was here, and it happens in Star Wars for some of the very same reasons.
"Help me, Obi-don Quixote. You're my only hope!"
(ahem)
Okay, my two cents on light sabers -- a few years ago I read another article that talked about how Star Wars tech might, maybe, perhaps work. The author consulted some physicists blah blah blah and suggested that the term light saber is intended to be descriptive by appearance but not by mechanism -- that a plasma controlled by a very powerful electromagnet could be made to appear not unlike the blade of a light saber -- the "blade" would actually be a tight loop, but you really couldn't notice the difference in the glow. Of course, it'd take more than a couple of "D" cells to power the thing...
I concur. While I may disagree with their presumed motivations, I like that the proposed definition describes the *process* of science -- which I agree is what science is all about, the process of creating knowledge.
Of course (TANGENT ALERT!), the remaining reference to "natural phenomena" still precludes even the question "is computer science a science?"
Has the military really given up on this concept, or has their research moved to other, more classified levels
I'd tell you, but then I'd have to kill you.
Ah, what the hell. I'll kill you anyway.
Hmm... I could scrap my cable modem and set up a Yagi pointing toward downtown Dayton. You think 20 or so elements would get me enough gain from Xenia?
In "Where No Man Has Gone Before" and "The Cage", the women wore pants, not miniskirts. It stands to reason that when Kirk, Spock, and McCoy were cadets, the skirts weren't the uniform of the day.
So... you are expecting the Spanish Inquisition?
Something else that I noticed (hmm... maybe this is something for which I could prepare a grant request to study...) -- back when I was working on my master's thesis, I noticed one of the other guys in the lab was two-finger typing -- just two index fingers curved at 90' angles. Naturally, I teased him about it. The thing of it is, you really couldn't call it hunt-and-peck, since he "knew" exactly where the keys were. All the motion was at the elbows and (to a lesser degree) the shoulders. He was probably going at a good 40-50 wpm, which is certainly slower than I can touch-type, but he never once rubbed his knuckles or wrists.
I just checked -- 13 April 2029 is a Friday.
Patients, we is. Yes, patients. We waits for our boxed set, our preciousssss.
Seems to me the guy's complaining about a primary aspect of the GPL -- that there are no restriction as to who can use the software.
Lindos == Linux Desktop Operating System
Well, I might be tempted to panic... except I voluntarily raised my right hand almost fifteen years ago and haven't yet been tempted away.
I've got an email inbox filled with "The Latest Security Update for Windows". I'd be careful before installing a patch from an unknown source.
OTOH, at least in this case, specific instances of code that has allegedly been copied from one to the other are provided.
The woman in the red dress should enter, natch.
And assure starvation freedom for philosophers everywhere.
They really should use The Library of Congress' Classification -- it's currently in use by (most?) libraries, and no one owns a trademark on it!
No sweat. Your mistake was assuming the accuracy of CNN ;D.
This, the same CNN that during the 1997 northern plains flooding, expressed concern that "now that Grand Forks (North Dakota) has suffered, the residents of Fargo are nervous", until apparently someone pointed out that Fargo had been flooded a couple days previous, that Fargo was upriver from Grand Forks. So then the map showed Fargo located north of Grand Forks (after all, we all know rivers flow down on the map). More blatantly was about a year before (but I don't remember the news story) when they showed North Dakota labeled "South Dakota" and vice-versa. Whoda thunk that South Dakota was actually north of North Dakota!?
cb
CNN
Witnesses said the object appeared to be traveling from southeast to northwest, "which means it was heading inland," Baalke said. fjordboy
At about 6:30 EST this evening, many meteors broke apart and headed south coming from Canada. Someone's confused.
cb
I am not dismissing the value of this work, but so long as developer & maintainer time is more valuable than processor time, when you choose a language, you should consider how well each language will make the developers' and (especially) the maintainers' jobs easier.
An example of how this can be considered is found in the appendices of "A Gentle Introduction to Software Engineering" (2,565 KB; MS Word format) by the Air Force's Software Technology Support Center (STSC). The appendices come from a document written in March 1996, so it's a little dated (predates the C++ standard, does not address Java, Python, or Perl), but the idea is there. (I like that it keeps repeating "Bad programmers can write bad code in any language, but a good language facilitates the production of good code by good programmers.".)
Including the performance achievable with each language is already in the formulation offered by STSC. The obvious caveat is that you look at the performance of benchmarks related to your application.
cb
Of course, that was 14 years ago.
cb
The "tubes" appear to be an optical illusion. Look especially in "Tubes 1". Look at the shadows on the crater in the upper right, then look at the shadows in the "tube". It appears to be a valley, not a tube. The "tiger-stripe" ridging is the result of the cliff edge slumping. Likewise, the "track" is a slumped cliff edge. The triangles are shadows in a dune field.
cb
See
a
lawyer
At a minimum, I expect the only way to avoid a conflict of interest is to recuse yourself from this project for your company. Even still, this may not be enough, since what you're working on at home is, by your description, something your employer would want to market.
cb
I think a couple issues need to be clarified. As a general rule, when the government contracts out for original software development, the copyright is held by the contractor (or whomever the contractor may assign it to). When the government hires an employee to develop software, then the government "owns" it, in the sense that the employee cannot claim copyright on it. By law, however, with rare exception (such as government-owned academic institutions), works developed by the government are not copyrighted.
If your employer, the contractor, believes it owns the copyright, that's between you and your employer. If, for some reason, DoD has a legitimate claim of ownership, then it's public domain.
Incidentally, the third option -- a government employee developing software while off-duty, using only his/her own equipment, and not as part of his/her official duties -- then the employee keeps the copyright, but the government will insist on a no-cost license for government use.
cb