The problem is over-generalization, and the fallacy of universal ethics/moral. Feminazi don't recognize that a women can actually enjoy being the object of sexual fetishism and/or objectified. Heck, I enjoy that too.
My point exactly. We never wanted to fight, but we won't give up our balls without a fight. Dear feminazi, you'll get my balls from my cold dead hands !
They're both nothing more than, "I don't approve of your beliefs."
Feminism used to be about equal rights, sexual freedom, and the right to do whatever a girl wanted with her body (including being gangbang'ed for her birthday by perfect strangers). What you describe is feminazism.
Women and men ARE different. We would not use two different word if they weren't. Can a women do 20 perfect form pullups ? Yes, sure, but it will take her a lot more effort and dedication to meet that goal than a man.
Yes it is, in today's society sexism is inappropriate.
Only if feminist/sjw achieve their petty agenda, but they won't get there without a fight. None of us wanted that fight, but we are left with no chance but to try to protect our balls.
Seriously, a basic typo on the title of a news make it to the front page ? I'm all for giving/. a chance wrt. the poor quality of article and the associated criticizes, but this is pushing it a bit far...
A3 prevention-focused defenses are concentrated in the Crumple Zones (CZs). The CZs essentially impose a space-time dilation upon the application’s interaction
oh, my... I'll keep reading the paper, but this is already buzzword-bingo ready.
... speechless incompetence is right. You're ranting about change that occurred in and cause problems because your customer skipped 3 versions of the OS and 6 years of updates...
I'd say speechless incompetence would be the guy who didn't do proper testing.
I'd love for you to point out this change you're referring though since this pretty much sounds exactly like the sort of thing FBSD is known for NOT doing.
Are you kidding ? You should grep the tree for __FreeBSD_version to find about the mess they are creating.
Let's rant about the kernel internals, and FreeBSD committers utterly brainfucked engineering decisons:
In FreeBSD 8, a KPI has been renamed. Though FreeBSD committers decided to reuse the old KPI's namespace, and the exact same prototypes, for a new a new KPI. This resulted in a totally transparent change code wise. Though, at the end of the game, codes which was working fine in FreeBSD 7 panic'ed in FreeBSD 10 . I found about this yesterday while debugging a failed assertion for a a customer of mine updating their codebase.
Speechless incompetence.... Though, keep at the bad work, fixing your incompetence is putting food on my table !
This isn't theft. Theft implies a loss, which does not happen with code. The original author still has his code. At worth, this is copyright infringement, which it might not even be if the original code was either public domain or opensource. Big entertainment have been trying the DRM way to limit it, with the known [lack of] success.
I'll be busy trying to succeed while you'll be busy trying to stop me succeeding. At the end innovation will still only come from me, and you'll be the jealous parasite.
You're not getting my point. If you need to write your own list implementation, you're not doing your job right. Use existing API. And that's gonna me my answer if that is the question during the next interview: "While I know the difference, this subject don't matter. If your company is worrying about efficiency of a list algorithm, you're most likely doing something wrong. You are not looking for me to write a list API, you're looking for me to write much higher level code. If the environment you are using don't provide a list API, you are in trouble."
Whether it is a vice or virtue is irrelevant. What matter is that everyone follows its values. For some it will be honor, for other, it will just be being successful no matter what the actions. FWIW, I prefer living a life on vice in hell rather than a life of virtue in paradise, ymmv.
Still, that does not justify the policy. A student with good lawyer/social connection will be able to have his name cleared, and one without who just needed those extra credit will get fucked. At the end of the line, the cheaters will not be able to function in a company, or might cheat their way out all their lives, but who cares ? If it's working for them, then it's the right way to behave.
Nobody gives a shit in the industry whose code is being included as long as the end product is working. If I am in a hurry, and a piece of GPL code is doing what I want, I'll copy/paste/reformat/adjust it, even if my target end software is proprietary. Heck, sometime, even the company is stealing part of GPL software for their purpose. My former company had originally hacked away wget to re-purpose its parsing capability in their proprietary code, I even updated the code base to a newer wget to get more feature. AFAIK, this "feature" has been deprecated today, more because the market evolved and customer didn't want that anymore rather than by any moral purpose.
Who gives a shit ? I once got an interview to port an OS on an embedded device. I pretty much knew jack shit about the terms the company was describing / asking me questions about, but I was capable of giving a description of the whole system. Said otherwise, my theory sucked, but my practice rocked. At the end, I got the internship (but didn't choose it; the pay sucked). You can know by heart the difference between a linked list and an array, but you can still be the worst programmer ever.
This is bs. Say I have to write a PNG as part of my program, do I go through the opening process of the PNG all by myself or do I just copy/paste the PNG opening code from the manpage ? I did the latter at school, with the proper disclamer "WARNING, PLAGIAT DETECTED. This code is directly stolen from the manpage, ooth there isn't 10^14 way to open a PNG". By your standard, I should re-code the PNG file from the binary data, heck, I should even re-code the POSIX API used to read/write the file and do basic stuff.
Slashdot Mirror
The problem is over-generalization, and the fallacy of universal ethics/moral. Feminazi don't recognize that a women can actually enjoy being the object of sexual fetishism and/or objectified. Heck, I enjoy that too.
My point exactly. We never wanted to fight, but we won't give up our balls without a fight. Dear feminazi, you'll get my balls from my cold dead hands !
It's not feminism anymore; it's puritanism. ...
There's a difference?
They're both nothing more than, "I don't approve of your beliefs."
Feminism used to be about equal rights, sexual freedom, and the right to do whatever a girl wanted with her body (including being gangbang'ed for her birthday by perfect strangers). What you describe is feminazism.
Pretty much.
Women and men ARE different. We would not use two different word if they weren't. Can a women do 20 perfect form pullups ? Yes, sure, but it will take her a lot more effort and dedication to meet that goal than a man.
Yes it is, in today's society sexism is inappropriate.
Only if feminist/sjw achieve their petty agenda, but they won't get there without a fight. None of us wanted that fight, but we are left with no chance but to try to protect our balls.
cf http://www.buzzfeed.com/davidm...
Seriously, a basic typo on the title of a news make it to the front page ? I'm all for giving /. a chance wrt. the poor quality of article and the associated criticizes, but this is pushing it a bit far...
and that's a $1,253,976.00 bingo... kinda expansive :-/
We use Xen 3.1.4 with Fedora Core 8 (kernel 2.6.18.8) images for both Dom0 and three DomUs in the prototype A3 environment.
2.6.18 ? Seriously ?
Come on, this is a buzzword heavy paper. It looks like some team failed to reach their quota of papers...
A3 prevention-focused defenses are concentrated in the Crumple Zones (CZs). The CZs essentially impose a space-time dilation upon the application’s interaction
oh, my... I'll keep reading the paper, but this is already buzzword-bingo ready.
You must not have recent graphics. Their i915 driver is largely outdated, and the update is laughably a ripoff of Linux' 3.8.
... speechless incompetence is right. You're ranting about change that occurred in and cause problems because your customer skipped 3 versions of the OS and 6 years of updates ...
I'd say speechless incompetence would be the guy who didn't do proper testing.
I'd love for you to point out this change you're referring though since this pretty much sounds exactly like the sort of thing FBSD is known for NOT doing.
Are you kidding ? You should grep the tree for __FreeBSD_version to find about the mess they are creating.
Let's rant about the kernel internals, and FreeBSD committers utterly brainfucked engineering decisons:
In FreeBSD 8, a KPI has been renamed. Though FreeBSD committers decided to reuse the old KPI's namespace, and the exact same prototypes, for a new a new KPI. This resulted in a totally transparent change code wise. Though, at the end of the game, codes which was working fine in FreeBSD 7 panic'ed in FreeBSD 10 . I found about this yesterday while debugging a failed assertion for a a customer of mine updating their codebase.
Speechless incompetence.... Though, keep at the bad work, fixing your incompetence is putting food on my table !
This isn't theft. Theft implies a loss, which does not happen with code. The original author still has his code. At worth, this is copyright infringement, which it might not even be if the original code was either public domain or opensource. Big entertainment have been trying the DRM way to limit it, with the known [lack of] success.
Thanks for the compliment. Not only will I survive your nuclear annihilation, and even worst, but I'll feed on you.
I'll be busy trying to succeed while you'll be busy trying to stop me succeeding. At the end innovation will still only come from me, and you'll be the jealous parasite.
You're not getting my point. If you need to write your own list implementation, you're not doing your job right. Use existing API. And that's gonna me my answer if that is the question during the next interview: "While I know the difference, this subject don't matter. If your company is worrying about efficiency of a list algorithm, you're most likely doing something wrong. You are not looking for me to write a list API, you're looking for me to write much higher level code. If the environment you are using don't provide a list API, you are in trouble."
Whether it is a vice or virtue is irrelevant. What matter is that everyone follows its values. For some it will be honor, for other, it will just be being successful no matter what the actions. FWIW, I prefer living a life on vice in hell rather than a life of virtue in paradise, ymmv.
Still, that does not justify the policy. A student with good lawyer/social connection will be able to have his name cleared, and one without who just needed those extra credit will get fucked. At the end of the line, the cheaters will not be able to function in a company, or might cheat their way out all their lives, but who cares ? If it's working for them, then it's the right way to behave.
Nobody gives a shit in the industry whose code is being included as long as the end product is working. If I am in a hurry, and a piece of GPL code is doing what I want, I'll copy/paste/reformat/adjust it, even if my target end software is proprietary. Heck, sometime, even the company is stealing part of GPL software for their purpose. My former company had originally hacked away wget to re-purpose its parsing capability in their proprietary code, I even updated the code base to a newer wget to get more feature. AFAIK, this "feature" has been deprecated today, more because the market evolved and customer didn't want that anymore rather than by any moral purpose.
Who gives a shit ? I once got an interview to port an OS on an embedded device. I pretty much knew jack shit about the terms the company was describing / asking me questions about, but I was capable of giving a description of the whole system. Said otherwise, my theory sucked, but my practice rocked. At the end, I got the internship (but didn't choose it; the pay sucked). You can know by heart the difference between a linked list and an array, but you can still be the worst programmer ever.
Rule #1: never talk to the police (or in this case, whatever authority who's gone on a fishing trip)
This is bs. Say I have to write a PNG as part of my program, do I go through the opening process of the PNG all by myself or do I just copy/paste the PNG opening code from the manpage ? I did the latter at school, with the proper disclamer "WARNING, PLAGIAT DETECTED. This code is directly stolen from the manpage, ooth there isn't 10^14 way to open a PNG". By your standard, I should re-code the PNG file from the binary data, heck, I should even re-code the POSIX API used to read/write the file and do basic stuff.