There is NO scientific proof that rape is about power. Feminists like to politicize the act, so that it fits in with the whole male patriarchal domination meme.
It's obviously not about power when someone rapes another person who has passed out - no power is needed, nor received - just sex. Same with young kids. Same with old people.
I've seen lots of indications that many men seem to think that they have some sort of right to or claim for sex with women under certain circumstances.
That has nothing to do with rape being about power - it backs up "rape is about sex". They feel that buying you a meal "pays" for sex. If it were about power, they wouldn't feel the need to "pay" for it.
I'd think hiring prostitutes would generally be easier, and not nearly as risky
And some people do pay for sex. Same as some think that a meal and a movie is "payment" for sex. Doesn't change the fact that there is no scientific evidence to back up the claim that rape is about power. They're all different mechanisms to what is obviously the same end.
Making it about power, since it obscures the truth, is actually doing a disservice to rape victims - that narrative implies that women have less power, and is a defeatist attitude. Also, if you're told repeatedly that it's about power, you're going to feel that maybe it's your fault because you weren't "socially powerful enough." Saying it's about sex takes away that whole dynamic. This is one of the bigger mind games that feminists have screwed women over with. It might fit their misanthropic all-men-are-pricks agenda, but it's wrong from the get-go.
Also, if it were about power, why do we criminalize it? It's about non-consensual sex.
Networking them one-way is easy enough. A stand-off AWACS broadcasts all the position information to every drone.
Also, an airplane that is stealth head-on is much more visible to radar from the side or bottom. Again, just make a general broadcast of target info. Networks don't have to be 2-way to be useful. And today's stealth technology has been defeated by going back to WW2-style radars with lower frequencies (someone forgot to check, so this was discovered by accident).
You were claiming trhat ISAMs were old, obsolete tech. I said otherwise - that they were old, but far from complete. Don't try to reframe the argument.
And MVCC isn't something new either. And replication? Come on - that's been around for decades.
And if the launchers use the same tactics as the SSN - keep all other friendlies away, so anything you encounter is an enemy to be destroyed - they can be autonomous. Launch and forget.
"Several more years" is not a decade. You could have even been the same age, just the other guy had several more years experience. Or they could have just told you that to ease the sting of telling you that you didn't make the cut.
Context is important. I was replying to the person who was claimed that hover states and mouse overs were too complicated to automate, pointing out that wasn't even true 20 years ago.
Anyone who thinks that hover states and css are all that hard needs to find another line of work.
Bean counters have the ultimate defense - it's not their fault, so not their problem. Remember, sh*t rolls downhill, and you and other cogs are at the bottom.
IE was the #1 browser at the time. Also, my point, which you totally failed to address, was that code generators were automatically doing the roll-over and hover states 2 decades ago - it's really simple code, and it can be done several different ways. If you can't even do that, you should find another job until you've learned how to do the basics.
When Apple sells a defective power cord that was made by someone else under license, it's Apple that is on the hook for the $$$, even though they didn't make it. Licensing deals will always get you dragged into a case - that's what lawyers, at least the competent ones, do.
Also, since a licensing deal for the visual design for use in producing a Batmobile necessitates the addition of an automobile chassis, if the licencor doesn't specify which chassis are approved for use, they can be held partially liable for licensing a defective product.
Since it's the majority of projects, it's obvious what the trend is, and it's getting rid of older programmers for cheaper young'uns who you can burn out and toss.
To management, you are a cog. As you get older, you become a more expensive cog that is also harder to abuse and drag out more hours because you have other commitments in your personal life that you are not willing to sacrifice, that younger people aren't weighed down with.
And then there's health problems. Need 6 months to a year off for pregnancy or a health issue, your job is gone. It's not like reclaiming a job on a assembly line. The person who filled in for you is now too deeply involved in the current projects to make it worthwhile to brig you up to speed. As you get older, this becomes more and more likely, and your ability to just bounce back erodes.
"Misses the whole NoSQL movement"???? Funny how renaming database techniques that preceded RDBMs as "NoSQL" turns it into a "new movement." Like ugly christmas sweaters that if you wait long enough come back into fashion, everything old is new again.
We are simply not seeing new categories of software on a regular basis. It's all information storage and retrieval, networked communications, word processing and spreadsheets, and games. We don't need 1,000 different word processors, 500 different spreadsheets, 200 different data store types, and 100 different networking architectures. Games? Even Minecraft can be seen as an extension of principles laid down in sim city, and todays FPS games are the same as always, just better graphics.
According to Janel Garvin, CEO of Evans Data, the thought of obsolescence due to A.I., "was also more threatening than becoming old without a pension, being stifled at work by bad management, or by seeing their skills and tools become irrelevant."
That's because everyone already is confronting becoming old without a pension, being stifled at work by bad management, seeing their skills and tools become irrelevant, being off-shored/out-sourced, being seen as too old when they have decades to go before becoming a senior, mass layoffs, mergers that entail "synergies" that really mean RIFs, economic crashes, jobless recoveries, divorce, kids, crime and terr'rism, racism, the collapsing safety net, being bankrupted by health problems despite having insurance...
Being replaced by AI is about the only fear that we haven't experienced yet.
That line of reasoning is full of crap. It doesn't take 100,000 times more programmers to produce a program uses 100,000,000 people than it does for 1,000. Most software is already "good enough." Much of it has been tinkered to death (firefox is a good example).
How many more word processors, spreadsheets, operating systems, social media platforms, and web browsers do we need anyway? People tend to use what other people are using. Cost is secondary (otherwise people would be running free platforms exclusively).
However, most of today's programmers will find that they're out of a job well before they're a senior citizen. Approaching your 40s, you start looking too old and too expensive compared to a young punk.
Today's programmers should be worried about being replaced by the 20-somethings, just like when they were 20-something, they did the same to the 40-year-old "codgers."
If you're over 30, you're far more likely to be replaced in the next 5-10 years by some wet-behind-the-ears punk than by a robot. And if you're in your 40s and still coding, the market says you're well past your "best before" date.
Slashdot Mirror
So you'll hit the big 5-0 in less than 10 years. Watch how quickly things can change.
For further reading - rapists enjoy consensual sex more than rape sex, and they enjoy violent rape sex the least. So much for power theories.
Even rapists say it was about sex, not power. Rapists rape for sex, same as bank robbers rob banks for money. Neither does it for power.
There is NO scientific proof that rape is about power. Feminists like to politicize the act, so that it fits in with the whole male patriarchal domination meme.
It's obviously not about power when someone rapes another person who has passed out - no power is needed, nor received - just sex. Same with young kids. Same with old people.
I've seen lots of indications that many men seem to think that they have some sort of right to or claim for sex with women under certain circumstances.
That has nothing to do with rape being about power - it backs up "rape is about sex". They feel that buying you a meal "pays" for sex. If it were about power, they wouldn't feel the need to "pay" for it.
I'd think hiring prostitutes would generally be easier, and not nearly as risky
And some people do pay for sex. Same as some think that a meal and a movie is "payment" for sex. Doesn't change the fact that there is no scientific evidence to back up the claim that rape is about power. They're all different mechanisms to what is obviously the same end.
Making it about power, since it obscures the truth, is actually doing a disservice to rape victims - that narrative implies that women have less power, and is a defeatist attitude. Also, if you're told repeatedly that it's about power, you're going to feel that maybe it's your fault because you weren't "socially powerful enough." Saying it's about sex takes away that whole dynamic. This is one of the bigger mind games that feminists have screwed women over with. It might fit their misanthropic all-men-are-pricks agenda, but it's wrong from the get-go.
Also, if it were about power, why do we criminalize it? It's about non-consensual sex.
Networking them one-way is easy enough. A stand-off AWACS broadcasts all the position information to every drone.
Also, an airplane that is stealth head-on is much more visible to radar from the side or bottom. Again, just make a general broadcast of target info. Networks don't have to be 2-way to be useful. And today's stealth technology has been defeated by going back to WW2-style radars with lower frequencies (someone forgot to check, so this was discovered by accident).
And MVCC isn't something new either. And replication? Come on - that's been around for decades.
It's easier to just scrap the photoshop crap and redo it using an image editor.
Here's a hint - the age spread of developers was not homogeneous. Having 1, of how many?
And if the launchers use the same tactics as the SSN - keep all other friendlies away, so anything you encounter is an enemy to be destroyed - they can be autonomous. Launch and forget.
And they will be totally useless against howitzers lobbing shells from +20 miles away.
Defeated by networked radar systems, same as stealth, since they would be hunting the radar source, which will be miles away and off the flight path.
Well, I sas "With a Bang" in the title and said to myself "Oh, no, not THAT guy again."
And yet RDBMs use ISAMs as part of their design to create and search records.
"Several more years" is not a decade. You could have even been the same age, just the other guy had several more years experience. Or they could have just told you that to ease the sting of telling you that you didn't make the cut.
Anyone who thinks that hover states and css are all that hard needs to find another line of work.
Bean counters have the ultimate defense - it's not their fault, so not their problem. Remember, sh*t rolls downhill, and you and other cogs are at the bottom.
Don't worry - your time will come. :-(
IE was the #1 browser at the time. Also, my point, which you totally failed to address, was that code generators were automatically doing the roll-over and hover states 2 decades ago - it's really simple code, and it can be done several different ways. If you can't even do that, you should find another job until you've learned how to do the basics.
If you can be ordered to pay out $5 billion to compensate one family, none of whom died, because a drunk driver slammed into the back of their 14-year-old car, anything is possible.
When Apple sells a defective power cord that was made by someone else under license, it's Apple that is on the hook for the $$$, even though they didn't make it. Licensing deals will always get you dragged into a case - that's what lawyers, at least the competent ones, do.
Also, since a licensing deal for the visual design for use in producing a Batmobile necessitates the addition of an automobile chassis, if the licencor doesn't specify which chassis are approved for use, they can be held partially liable for licensing a defective product.
Since it's the majority of projects, it's obvious what the trend is, and it's getting rid of older programmers for cheaper young'uns who you can burn out and toss.
To management, you are a cog. As you get older, you become a more expensive cog that is also harder to abuse and drag out more hours because you have other commitments in your personal life that you are not willing to sacrifice, that younger people aren't weighed down with.
And then there's health problems. Need 6 months to a year off for pregnancy or a health issue, your job is gone. It's not like reclaiming a job on a assembly line. The person who filled in for you is now too deeply involved in the current projects to make it worthwhile to brig you up to speed. As you get older, this becomes more and more likely, and your ability to just bounce back erodes.
"Misses the whole NoSQL movement"???? Funny how renaming database techniques that preceded RDBMs as "NoSQL" turns it into a "new movement." Like ugly christmas sweaters that if you wait long enough come back into fashion, everything old is new again.
We are simply not seeing new categories of software on a regular basis. It's all information storage and retrieval, networked communications, word processing and spreadsheets, and games. We don't need 1,000 different word processors, 500 different spreadsheets, 200 different data store types, and 100 different networking architectures. Games? Even Minecraft can be seen as an extension of principles laid down in sim city, and todays FPS games are the same as always, just better graphics.
This crossover into hardware means that no simple pure software AI will ever take over the task
Chip and motherboard layout is already almost exclusively done by computers.
According to Janel Garvin, CEO of Evans Data, the thought of obsolescence due to A.I., "was also more threatening than becoming old without a pension, being stifled at work by bad management, or by seeing their skills and tools become irrelevant."
That's because everyone already is confronting becoming old without a pension, being stifled at work by bad management, seeing their skills and tools become irrelevant, being off-shored/out-sourced, being seen as too old when they have decades to go before becoming a senior, mass layoffs, mergers that entail "synergies" that really mean RIFs, economic crashes, jobless recoveries, divorce, kids, crime and terr'rism, racism, the collapsing safety net, being bankrupted by health problems despite having insurance ...
Being replaced by AI is about the only fear that we haven't experienced yet.
That line of reasoning is full of crap. It doesn't take 100,000 times more programmers to produce a program uses 100,000,000 people than it does for 1,000. Most software is already "good enough." Much of it has been tinkered to death (firefox is a good example).
How many more word processors, spreadsheets, operating systems, social media platforms, and web browsers do we need anyway? People tend to use what other people are using. Cost is secondary (otherwise people would be running free platforms exclusively).
However, most of today's programmers will find that they're out of a job well before they're a senior citizen. Approaching your 40s, you start looking too old and too expensive compared to a young punk.
Today's programmers should be worried about being replaced by the 20-somethings, just like when they were 20-something, they did the same to the 40-year-old "codgers."
If you're over 30, you're far more likely to be replaced in the next 5-10 years by some wet-behind-the-ears punk than by a robot. And if you're in your 40s and still coding, the market says you're well past your "best before" date.
Most of them have CMS systems that a non-programmer can customize.