1) I'm fairly certain the plane was low 2) Trans-Atlantic? Hell, I lose reception on lonely stretches of Interstate Highway, so sure, I'd expect little to no cell/cdma/pcs/wtf service while out there.
Granted, it takes the airlines forever to agree to small safety changes like, oh, I don't know... Installing non-flammable seat cushions?!? I guess we can't really expect too much in the way of retrofits, particularly in today's economic climate.
We bail 'em out, they waste it, we'll just bail 'em out again.
I'd REALLY REALLY REALLY like to see Boeing, Airbus et al. installing avionics and comms systems that can't be disrupted by ubiquitous and nearly free techno-gadgets.
Cut broadcast radio, too! Let's trick those darned aliens monitoring us into thinking we blew each other up or something.
The IP feudal system
on
Latest SCO News
·
· Score: 2, Insightful
I've been noticing the byzantine complexity of the licensing agreements, and I think it bears a striking resemblance to the medieval European feudal system.
Granted, we use the terms IP, patent and copyright instead of fealty, vassal and liege lord, but the end effect seems similar. Conflicted loyalties and unresolved questions pile atop one another until the whole mess comes crashing down on everyone's heads.
It's not that I am charging for my IP. It's that the terms of my contractual agreement dictate ownership of work I create during my paid business hours.
I personally do not have a moral or ethical quandary with opening up my development process, busting a hole in the firewall to allow CVS or at least SSH access, and making wholesale changes to open source projects on company time. I just don't want to be the subject of a 'Your Rights Online' story here.
It's part of my personality naturally, and when navigating the American legal system, it's an asset.
Essentially the facts are as follows: I code for fun, and I code for money. When I'm coding for money, there are expectations, and those expectations include copyrighting the code. When I code for fun, Eclipse generates GPL templates automagically for every source module I create.
More than one fellow has tried to engage me in business ventures during work hours, but I'm always careful to defer all such discussions to a time and place where I can truly consider myself free.
I'm a consultant, paid for my time and the IP I develop. I would not dare to risk cross-contamination by doing anything more than downloading and using open-source packages at the office.
I'm pretty sure we all find spam to be terribly annoying, but I for one don't think it costs me much more than time and energy... Granted, I'd rather NOT have to expend those in an effort to keep my penis from growing so large it frightens everyone I meet.
I've come to believe that you can learn a lot about a person or organization based upon their treatment of others. If one's mind is a world of sexual perversion, one sees child pornography in the innocent bathtime photos parents take of their kids. If one's mind is a prime example of a money-grubbing, to-hell-with-everyone-else attitude, one sees piracy in every PC.
In this case, it's apparent that the BSA and it's leaders are rapacious, greedy, amoral takers of other people's goods. They should be put away for their own safety and ours.
Re:Why not just rewrite the offending code?
on
SCO SCO SCO!
·
· Score: 1
The trouble is, you are attempting to offer a logical solution to the stated problem. However, the stated problem is a lie, and has no bearing on the actual case that McBride and Co. are attempting to drive the stock price higher and achieve buyout.
Doing as you suggest would eliminate any basis for a lawsuit, and also for SCO's value in the marketplace.
What I most greatly fear is that some judge will be handed a mass of program listings, with large blocks of #include statements and such highlighted as being 'infringing'. Even header files themselves, defining constants, would probably work on a lot of the old farts. Fortunately, IBM ain't stupid about lawsuits, and their lawyers should be well versed in countering those moves.
Pay to watch them shooting a movie I probably won't bother bringing myself to pay to see?
Not bloody likely.
Star Wars was hot in the '70s, cool in the '80s, retro in the '90s, and turned into a joke by the Phantom Menace. When I first saw that they were setting up a webcam, I thought it was mildly interesting. The pay thing is the final proof I needed though, that the SW franchise has had enough of my attention.
LOL! That's because in the US the poverty line is something like fifteen thousand dollars a year! There are plenty of places where you could live VERY well on that kind of scratch.
Somehow, no matter what you or anyone says about our 'rate of poverty', I'd rather be here than Somalia, y'know?
In the news: Hackers at a web site called 'slash-dot' (we believe it to be a hate-site against Indian developers) have instituted a denial-of-service attack against CIA web servers. Teams are currently raiding several OSDN locations in order to preserve freedom.
After all, it's only within the past month that I signed both my wife and myself up for two years of new service, locking us out of upgrading for a while.
To all those who are planning to get a wristphone: You're welcome.
What really gets me is this: SCO is as much as admitting that all they have to do is announce what is duplicated, and the open source community will clean it up quickly. So what they're actually doing, by their logic, is harming THEMSELVES by not quickly forcing code changes.
The REAL issue here of course is IBM's AIX product, and the licensing for it that expires in a couple of months. SCO isn't hoping to win this lawsuit, they're hoping to be either acquired or simply paid off by IBM.
Slashdot Mirror
1) I'm fairly certain the plane was low
2) Trans-Atlantic? Hell, I lose reception on lonely stretches of Interstate Highway, so sure, I'd expect little to no cell/cdma/pcs/wtf service while out there.
Granted, it takes the airlines forever to agree to small safety changes like, oh, I don't know... Installing non-flammable seat cushions?!? I guess we can't really expect too much in the way of retrofits, particularly in today's economic climate.
We bail 'em out, they waste it, we'll just bail 'em out again.
Of course. Remember the cell phone calls from the Pennsylvania flight on Sept. 11, 2001?
I'd REALLY REALLY REALLY like to see Boeing, Airbus et al. installing avionics and comms systems that can't be disrupted by ubiquitous and nearly free techno-gadgets.
I think it would be great. It's the marketing clods and PHBs who oversell capabilities, product, and deliverable dates.
Let's not even get started on Microsoft's legal status under such a regime.
Yeah, it's called a Daisy Cutter.
Cut broadcast radio, too! Let's trick those darned aliens monitoring us into thinking we blew each other up or something.
I've been noticing the byzantine complexity of the licensing agreements, and I think it bears a striking resemblance to the medieval European feudal system.
Granted, we use the terms IP, patent and copyright instead of fealty, vassal and liege lord, but the end effect seems similar. Conflicted loyalties and unresolved questions pile atop one another until the whole mess comes crashing down on everyone's heads.
It's not that I am charging for my IP. It's that the terms of my contractual agreement dictate ownership of work I create during my paid business hours.
I personally do not have a moral or ethical quandary with opening up my development process, busting a hole in the firewall to allow CVS or at least SSH access, and making wholesale changes to open source projects on company time. I just don't want to be the subject of a 'Your Rights Online' story here.
It's part of my personality naturally, and when navigating the American legal system, it's an asset.
Essentially the facts are as follows: I code for fun, and I code for money. When I'm coding for money, there are expectations, and those expectations include copyrighting the code. When I code for fun, Eclipse generates GPL templates automagically for every source module I create.
More than one fellow has tried to engage me in business ventures during work hours, but I'm always careful to defer all such discussions to a time and place where I can truly consider myself free.
No entanglements, low risk.
I'm a consultant, paid for my time and the IP I develop. I would not dare to risk cross-contamination by doing anything more than downloading and using open-source packages at the office.
Is that what this group believes?
I'm pretty sure we all find spam to be terribly annoying, but I for one don't think it costs me much more than time and energy... Granted, I'd rather NOT have to expend those in an effort to keep my penis from growing so large it frightens everyone I meet.
Well, it's not as though that 1% is a REAL number... It may, however, be a poorly-chosen lie.
I've come to believe that you can learn a lot about a person or organization based upon their treatment of others. If one's mind is a world of sexual perversion, one sees child pornography in the innocent bathtime photos parents take of their kids. If one's mind is a prime example of a money-grubbing, to-hell-with-everyone-else attitude, one sees piracy in every PC.
In this case, it's apparent that the BSA and it's leaders are rapacious, greedy, amoral takers of other people's goods. They should be put away for their own safety and ours.
The trouble is, you are attempting to offer a logical solution to the stated problem. However, the stated problem is a lie, and has no bearing on the actual case that McBride and Co. are attempting to drive the stock price higher and achieve buyout.
Doing as you suggest would eliminate any basis for a lawsuit, and also for SCO's value in the marketplace. What I most greatly fear is that some judge will be handed a mass of program listings, with large blocks of #include statements and such highlighted as being 'infringing'. Even header files themselves, defining constants, would probably work on a lot of the old farts. Fortunately, IBM ain't stupid about lawsuits, and their lawyers should be well versed in countering those moves.
LOL Dess, thats' a good'un.
Pay to watch them shooting a movie I probably won't bother bringing myself to pay to see?
Not bloody likely.
Star Wars was hot in the '70s, cool in the '80s, retro in the '90s, and turned into a joke by the Phantom Menace. When I first saw that they were setting up a webcam, I thought it was mildly interesting. The pay thing is the final proof I needed though, that the SW franchise has had enough of my attention.
LOL! That's because in the US the poverty line is something like fifteen thousand dollars a year! There are plenty of places where you could live VERY well on that kind of scratch.
Somehow, no matter what you or anyone says about our 'rate of poverty', I'd rather be here than Somalia, y'know?
In the news: Hackers at a web site called 'slash-dot' (we believe it to be a hate-site against Indian developers) have instituted a denial-of-service attack against CIA web servers. Teams are currently raiding several OSDN locations in order to preserve freedom.
-- John Ashcroft, here to help you
So.... You're saying that most current pop acts would be safe ripping off any works they want to, because noone enjoys hearing them anyway?
I suspect that Morgan Webb would be a lot more likely to consider you if you spelled her name correctly ;-)
Oh, I know... But I'm having a bit of fun.
;-)
Besides, she who must be obeyed wouldn't really enjoy me spending the money
It only makes sense.
After all, it's only within the past month that I signed both my wife and myself up for two years of new service, locking us out of upgrading for a while.
To all those who are planning to get a wristphone: You're welcome.
Heh...
Examples of line-by-line matching:
if(0 == i) {
i++;
}
And
while((c = fread(in) != null) {
elements[counter++] = c;
}
Imagine the nerve!
What really gets me is this: SCO is as much as admitting that all they have to do is announce what is duplicated, and the open source community will clean it up quickly. So what they're actually doing, by their logic, is harming THEMSELVES by not quickly forcing code changes.
The REAL issue here of course is IBM's AIX product, and the licensing for it that expires in a couple of months. SCO isn't hoping to win this lawsuit, they're hoping to be either acquired or simply paid off by IBM.
I suppose that depends on how old you are ;-)