Re:Why terrorism doesn’t work (2002) [pdf]
by bjourne on Wednesday November 02, 2016 @07:59AM
(#12853813)
Modern warfare makes the distinction tricky. Suppose you have a person sitting in a computer center in California controlling drones dropping bombs in Afghanistan. Is he a civilian or soldier? If not, does he become one when he goes home from his shift for the day? What about all the computer programmers writing drone software making his job possible?
Re:Why terrorism doesn’t work (2002) [pdf]
by nailer on Wednesday November 02, 2016 @10:32AM
(#12855102)
> Suppose you have a person sitting in a computer center in California controlling drones dropping bombs in Afghanistan. Is he a civilian or soldier?
They are a soldier, attacking an enemy. I genuinely don't understand how being further away makes that unclear.
Or any different from a soldier calling in an airstrike being further away than a soldier with a rifle being further away than a soldier with a sword.
> If not, does he become one when he goes home from his shift for the day?
They are an off duty soldier.
> What about all the computer programmers writing drone software making his job possible?
They are weapons manufacturers.
Re:Why terrorism doesn’t work (2002) [pdf]
by BBlarat on Wednesday November 02, 2016 @08:04AM
(#12853834)
Writing drone software = workers in a munitions factory? Valid military targets, at least to me. Same with the drone operator, which afaik is usually in the military, with military training.
Yes. So tired of this word being used to describe attacks on soldiers. It might be bad (depending on what side you're on), but it's certainly not terrorism.