First: congratulations, that worked out very well for you and the bully probably even deserved it. That took balls.
Even though I got more than my share of taunting, I couldn't recommend your solution to every picked-on person. What if you had accidentally crushed his skull instead of his larynx? As it is, I'm suprised you didn't get sued by the guy's parents. If you went Columbine on his ass today you might not get off so easily.
Also, some victims are very uncoordinated. I knew one guy who decided he had enough and tried to kick his bully in the balls. He mis-aimed. Whoops.
In either case, I'd have to either recommend some martial-arts training or boxing, so at least you could control the damage you were dealing out. OTOH you'd probably be held responsible for it, whereas I bet you got off with "I didn't know I could hurt him so bad"
Finally, as another poster pointed out, there are the kids you want to mess with as little as possible. You know, members of (insert your country)'s Future Violent Criminals Club. They're too stupid to understand that killing you in retaliation isn't worth it.
Nope. The Zilog z80 was a riced-out Intel 8080. The original 8086 (and 8088) was source-, but not binary-, compatible with the 8080. Google for "z80 8080" and "8086 8080" to verify.
*16%* of all CIOs were negatively influenced (seems unlikely that it's a positive influence) toward Linux because of this one SCO money grab.
It might be positive, if some of those CIOs are (were) SCO customers. Of course, the numbers are probably negligible enough not to impact your argument significantly:)
6 - that I can now be lazy at work, and get fired, or bust my ass at work, and get fired.
Very true -- but. External commitments and priorities aside, if you're learning a lot at your current job, and get fired, it's still better than learning nothing, and getting fired.
Also, they outsourced their engine construction which, seeing the kind of trouble Armadillo is having with their engines, might turn out to be a winning strategy.
It may be a losing strategy. They lose direct control over the design, test, and schedule of the engine. Last I checked, this was a pretty critical part, and it's also.. uh.. "rocket science". Hopefully the integration of the engine into the rest of the vehicle won't take too long.
We won't really know how this works out until Scaled issues some "rocket progress" reports.
I do understand why Scaled would outsource the engine work. It's not really the business they want to be in.
You're correct in that the executive office exerts much more power (relatively) over foreign relations than it does over domestic issues. The economy is usually in the hands of our Congress, although the prez usually gets the blame/credit for it, come election time.
Doing my best to bite my tongue on the foreign relations bit..
More proper wording which I would accept is, "Due to intellectual property issues and conflicts of interest, we regret that we cannot hire former employees of the Santa Cruz Operation at this time."
If this was strictly about IP concerns/being sued, Damage shouldn't have set a deadline to leave SCO. In fact they shouldn't have publically announced any SCO policy at all. They should have silently discarded resumes w/offending SCO experience. That way, you get fewer potential employees committing 'sins of omission' on their resume.
No, I think Damage is taking a stand. Which is fine w/me. It's their perogative and there's plenty of other companies out there, many of whom also aren't currently hiring:)
You shouldn't -- if you want the program you're using to die, that is.
That's overblowing things; there's a differenece between program "death" and program "stagnation". One of them, in theory, doesn't happen to Free Software.
it's also fair to the authors
Some authors don't care what you do. Some work for pizza and beer. Others run (in effect) a charity. Some actively maintain and improve their programs, and some don't/won't. Point is.. what and if you should contribute varies widely from author to author.
You've pretty much answered your question in the parenthesis. SCO has laid off most of its development staff, and there have been a few high-profile people quitting as well. What's left at SCO is mostly the legal team and a handful of salespeople.
There is (was) at least one SCO developer who posted to the GCC mailing list in August (not reposting his name here; download the mbox archive if you don't believe).
Can you provide more info or links to back up your assertions? Besides news on the Engineering VP, that is; I know he's gone.
.. and as long as we're keeping track, they at least used to be heavily involved w/XFree86 development. Particularly pre-4.0, when it *really* needed
work.
The interviews center around whether integration with proprietary products endangers the Open Source effort or increases consumers' freedom to choose."
And the answer is.. "Yes".
Thank you, please proceed to the next/. discussion.
The interesting issue is that SCO seems to be under the misapprehension that the BFP is their own code to begin with - that seems to imply that they illegally stripped a copyright notice somewhere along the way.
With the information given, it's quite plausible that AT&T originally copied BPF into sysv (sans copyright notice), and never bothered to put it back after the UC Berkeley settlement. Then SCO inherited the sysv mess.
They still deserve to burn, especially after Darl's fervent claims that "we are not talking about BSD code"! Talk about willful ignorance..
assuming the env is little-endian, alignment assumptions,... and wearing 32-bit blinds. Not really a linux system annoyance, but more a Linux-attitude-towards-other-systems and brainfarted programmer annoyance
All of these problems are "processor architecture", not OS, dependent. 'brainfarted programmer' is right on.
Slashdot Mirror
Even though I got more than my share of taunting, I couldn't recommend your solution to every picked-on person. What if you had accidentally crushed his skull instead of his larynx? As it is, I'm suprised you didn't get sued by the guy's parents. If you went Columbine on his ass today you might not get off so easily.
Also, some victims are very uncoordinated. I knew one guy who decided he had enough and tried to kick his bully in the balls. He mis-aimed. Whoops.
In either case, I'd have to either recommend some martial-arts training or boxing, so at least you could control the damage you were dealing out. OTOH you'd probably be held responsible for it, whereas I bet you got off with "I didn't know I could hurt him so bad"
Finally, as another poster pointed out, there are the kids you want to mess with as little as possible. You know, members of (insert your country)'s Future Violent Criminals Club. They're too stupid to understand that killing you in retaliation isn't worth it.
I'm not trying to be a wise-ass here... I'd recommend logging in remotely, "su -"ing to their username, reproducing their trouble, then fixing it.
The explanation is just "if it happens again, let me know".
Not that Windows doesn't have its strengths, but fixing things on that platform is usually more intrusive and confusing from the secretary's POV.
Nope. The Zilog z80 was a riced-out Intel 8080. The original 8086 (and 8088) was source-, but not binary-, compatible with the 8080. Google for "z80 8080" and "8086 8080" to verify.
It might be positive, if some of those CIOs are (were) SCO customers. Of course, the numbers are probably negligible enough not to impact your argument significantly :)
Yeah, but then nobody would play the state lottery, and my taxes would go up even more.
My evil business leader has ASKED me to spend serious time contributing back to an open source project that we use as our customer support system
There is certainly room for even more improvement. As long as I'm wishing, I'd like to see all the architectures share more common code, netbsd-style.
OTOH, at least the linux kernel doesn't still use the K&R coding style..
Very true -- but. External commitments and priorities aside, if you're learning a lot at your current job, and get fired, it's still better than learning nothing, and getting fired.
If you're lazy, you don't learn as much.
It may be a losing strategy. They lose direct control over the design, test, and schedule of the engine. Last I checked, this was a pretty critical part, and it's also.. uh.. "rocket science". Hopefully the integration of the engine into the rest of the vehicle won't take too long.
We won't really know how this works out until Scaled issues some "rocket progress" reports.
I do understand why Scaled would outsource the engine work. It's not really the business they want to be in.
You're correct in that the executive office exerts much more power (relatively) over foreign relations than it does over domestic issues. The economy is usually in the hands of our Congress, although the prez usually gets the blame/credit for it, come election time.
Doing my best to bite my tongue on the foreign relations bit..
Maybe if you wait long enough, it will dawn on you.
If this was strictly about IP concerns/being sued, Damage shouldn't have set a deadline to leave SCO. In fact they shouldn't have publically announced any SCO policy at all. They should have silently discarded resumes w/offending SCO experience. That way, you get fewer potential employees committing 'sins of omission' on their resume.
No, I think Damage is taking a stand. Which is fine w/me. It's their perogative and there's plenty of other companies out there, many of whom also aren't currently hiring :)
That's overblowing things; there's a differenece between program "death" and program "stagnation". One of them, in theory, doesn't happen to Free Software.
it's also fair to the authors
Some authors don't care what you do. Some work for pizza and beer. Others run (in effect) a charity. Some actively maintain and improve their programs, and some don't/won't. Point is.. what and if you should contribute varies widely from author to author.
There is (was) at least one SCO developer who posted to the GCC mailing list in August (not reposting his name here; download the mbox archive if you don't believe).
Can you provide more info or links to back up your assertions? Besides news on the Engineering VP, that is; I know he's gone.
Wasn't that right about when Apple decided that Microsoft wasn't "the enemy" and that Dell was?
(umm, I could be very wrong though, I don't pay much attention to Apple news.)
.. and as long as we're keeping track, they at least used to be heavily involved w/XFree86 development. Particularly pre-4.0, when it *really* needed work.
And the answer is.. "Yes".
Thank you, please proceed to the next /. discussion.
wget is what you want, folks. Happy browsing.
With the information given, it's quite plausible that AT&T originally copied BPF into sysv (sans copyright notice), and never bothered to put it back after the UC Berkeley settlement. Then SCO inherited the sysv mess.
They still deserve to burn, especially after Darl's fervent claims that "we are not talking about BSD code"! Talk about willful ignorance..
AC, I hate to point out the obvious, but when you want somebody to email you, it helps if you provide an address.
On the upside, it must be fun hanging out with Fire Marshall Bill.
All of these problems are "processor architecture", not OS, dependent. 'brainfarted programmer' is right on.
Best info I see on that is here, or possibly here, which doesn't quite dispel the "rumor"-ness of it (sorry).
I bet he's gone. I almost feel a little sorry for him -- you can bet he will be in court for awhile. I wonder whose side he will testify for?
Like, "I bought a /. t-shirt .. and all I got was this lousy t-shirt"
Yes, we like to call it Iraq.