The area had been quite for well over 5mins. Watch the unedited version. The entire city was an area with really loud cannon rounds all over the place all the time. The pilot even said they didn't have weapons but appeared to taking the wounded away, and "Fuck let us shoot". What rules of engagement is that? Lets not forget they lied about getting shot at in the first place.
Standing up for this will not help. Watch the full video, you even get a sense of the attitude between the ground forces and the airborne calvary unit.
Real soldiers who where there in Iraq are condemning these actions. Real pilots are too.
And lets not forget this is their *home city*. This is where they live, America made it a "war zone", where shooting unarmed people (by the pilots own admission) who are rescuing the wounded (a fellow country man) is apparently fair game for burst of 30mm cannon rounds by the American version of the rules of engagement.
If I was a middle eastern country right now, i would be very supportive of a government that was trying to get nukes. It seems to be the only way to be treated as a sovereign country.
Since when does rescuing the wounded *unarmed* get a kill on site order.
Try watching it. People *inside* the armed forces leaked this. They feel its wrong enough to leak. People who were in Iraq an saw the video also think its pretty bad.
But shooting a Family that did nothing but stop to pick a wounded man on the side of the road, is nothing short of a war crime. And the "don't bring kids to battle" doesn't work when its the US that took the battle to Baghdad (Where, shock horror, families live with children).
Judging from the delay of firing to impact I would say they where already well out of range. Also Apaches are not known for there quiet loiter, and yet no one really appears to be aware that there are gunships around (like the van rescuing the wounded, otherwise they may have thought twice about it).
The firing on the van though, without question, was a mistake...
Thinking a camera is rpg is incompetence and a mistake. Shooting on the van, no, begging to kill everyone in and outside the van, is a war crime. It was not a mistake. It was premeditated, clear cold bloody murder of civilians engaged in rescue.
Bear in mind its people inside the military that leaked this. So they clearly don't think this is just what happens in war.
It was not a 20 something sleep deprived jittery guy behind a machine guy. It was a gunner in a gunship more than half a mile away, that was begging to be given permission to rip though a civilian van that with unarmed civilians picking up a wounded man on the side walk.
The guy who begged to open fire on civilians that were attending to the wounded. In fact the guy was acting like evacuating the wounded was a crime worthy of a dozen 30mm rounds.
The man calling the shots, the man on the trigger, the man that claimed it was all rpgs and ak47. He is ultimately responsible.
Oh the nice side of this, clearly others involved (armed forces) think it is a f*** up too. Otherwise it wouldn't have made it too wikileaks. In fact i would go as far to say someone, probably more than one feels this is very very wrong and there should be hell to pay.
Shooting civilians assisting the wounded is a war crime. Begging to be given permission removes any excuses what so ever...What the hell is wrong with taking away the wounded. Sounded like he doesn't get frag point or something.
Yea cus its protocol to kill anyone unarmed and attending to the wounded. Its people like you in the armed forces that is the problem.
"Hay it looks like a weapon, so now i am allowed to kill em!" WTF? If you can't tell the difference what the hell are you doing in a gunship? If you can't even accept the consequences of killing civilians because you thought a TV camera and tripod was a RPG and ak-47 (why even state the type of rifle when you can't tell?) then you shouldn't be there.
Maybe these gun happy, incompetent, violent nut cases should have stayed home at the safety of their own computers... Since they feel so threated by a few reporters and TV camera, I don't think they have the stuff of real soldiers.
There is also zero evidence that it doesn't exist. Its a question that is not testable in the scientific sense. That makes it a non scientific question.
Only if *all* the library it links too are *also* 32 bit and only on the x86 version of 64bit where there is a hardware compatibility mode.
The point remains that even Ansi C can and often is written in a way that means it will only compile on one quite specific "system" for whatever definition of system you want.
And yet there is still a sizable code base in this "standard" C that won't compile for a 64bit CPU. And not just any 64bit CPU, but one thats so bloody close to the 32bit version that it supports both modes/instruction/register whatever.
So, in the end, unless we programmers get together and create our own suite of languages..
It would be the worst language of all time. Some ugly cross between python, java, and perl. if else would use 3 different spellings, typing would be optional and the C programmers will insist on direct access to pointers (and hence require an explicit known memory layout for most types) and require (void*) casts everywhere. Because of its total nastiness the compilers would be unable to do any escape analysis and other optimizations would be difficult too. Then the "C" coders will insist that to write fast code you need asm blocks and its all down the toilet. I haven't even got to namespaces, module systems, macros and linking conventions yet.
Despite what a lot of people think. The games market on PC/servers etc is pretty small. Sun was wise not to push it really. For games you would need Xbox..etc to support a jvm for it to really make sense. And that will not happen for a number of reasons.
However there is lwjgl (opengl/openal binding for java), and most common higher level languages can run on top of a JVM these days. (Jython, JScheme, Kawa, lua,....)
h.264 is not open. Sure you can read it, but if you code it up and then run that code, or give that code to others, you are breaking the law in a number of countries.
Perhaps reading the h.264 spec is enough for you... But open to me means open to use freely ie without cash or contract.
Slashdot Mirror
And being unarmed, as the pilot said they were, does make them a non-combatant. But hay we are team America, we kill who ever the fuck we like.
The area had been quite for well over 5mins. Watch the unedited version. The entire city was an area with really loud cannon rounds all over the place all the time. The pilot even said they didn't have weapons but appeared to taking the wounded away, and "Fuck let us shoot". What rules of engagement is that? Lets not forget they lied about getting shot at in the first place.
Standing up for this will not help. Watch the full video, you even get a sense of the attitude between the ground forces and the airborne calvary unit.
Real soldiers who where there in Iraq are condemning these actions. Real pilots are too.
And lets not forget this is their *home city*. This is where they live, America made it a "war zone", where shooting unarmed people (by the pilots own admission) who are rescuing the wounded (a fellow country man) is apparently fair game for burst of 30mm cannon rounds by the American version of the rules of engagement.
If I was a middle eastern country right now, i would be very supportive of a government that was trying to get nukes. It seems to be the only way to be treated as a sovereign country.
Since when does rescuing the wounded *unarmed* get a kill on site order.
They look like villains and terrorist because they are. Thats not based on anything but the raw, unedited video.
Either you didn't watch it, you are one of the pilots, or you think anyone that all non American should be shot.
Try watching it. People *inside* the armed forces leaked this. They feel its wrong enough to leak. People who were in Iraq an saw the video also think its pretty bad.
But shooting a Family that did nothing but stop to pick a wounded man on the side of the road, is nothing short of a war crime. And the "don't bring kids to battle" doesn't work when its the US that took the battle to Baghdad (Where, shock horror, families live with children).
Well it got to wikileaks because others inside the armed forces clearly feel the same.
Could the choppers have moved away..
Judging from the delay of firing to impact I would say they where already well out of range. Also Apaches are not known for there quiet loiter, and yet no one really appears to be aware that there are gunships around (like the van rescuing the wounded, otherwise they may have thought twice about it).
Frag count. His buddy got 27 kills the day before. And you can't count bodies that aren't there when the ground troops arrive.
The firing on the van though, without question, was a mistake...
Thinking a camera is rpg is incompetence and a mistake. Shooting on the van, no, begging to kill everyone in and outside the van, is a war crime. It was not a mistake. It was premeditated, clear cold bloody murder of civilians engaged in rescue.
Bear in mind its people inside the military that leaked this. So they clearly don't think this is just what happens in war.
It was not a 20 something sleep deprived jittery guy behind a machine guy. It was a gunner in a gunship more than half a mile away, that was begging to be given permission to rip though a civilian van that with unarmed civilians picking up a wounded man on the side walk.
the ultimate responsibility lies with....
The guy who begged to open fire on civilians that were attending to the wounded. In fact the guy was acting like evacuating the wounded was a crime worthy of a dozen 30mm rounds.
The man calling the shots, the man on the trigger, the man that claimed it was all rpgs and ak47. He is ultimately responsible.
Oh the nice side of this, clearly others involved (armed forces) think it is a f*** up too. Otherwise it wouldn't have made it too wikileaks. In fact i would go as far to say someone, probably more than one feels this is very very wrong and there should be hell to pay.
Shooting civilians assisting the wounded is a war crime. Begging to be given permission removes any excuses what so ever...What the hell is wrong with taking away the wounded. Sounded like he doesn't get frag point or something.
While things like this happen, and while the perpetrators are not brought to justice. You are your government. Whether by action or inaction.
Yea cus its protocol to kill anyone unarmed and attending to the wounded. Its people like you in the armed forces that is the problem.
"Hay it looks like a weapon, so now i am allowed to kill em!" WTF? If you can't tell the difference what the hell are you doing in a gunship? If you can't even accept the consequences of killing civilians because you thought a TV camera and tripod was a RPG and ak-47 (why even state the type of rifle when you can't tell?) then you shouldn't be there.
Maybe these gun happy, incompetent, violent nut cases should have stayed home at the safety of their own computers... Since they feel so threated by a few reporters and TV camera, I don't think they have the stuff of real soldiers.
There is also zero evidence that it doesn't exist. Its a question that is not testable in the scientific sense. That makes it a non scientific question.
Only if *all* the library it links too are *also* 32 bit and only on the x86 version of 64bit where there is a hardware compatibility mode.
The point remains that even Ansi C can and often is written in a way that means it will only compile on one quite specific "system" for whatever definition of system you want.
I don't think Bad Analogy means what you think it means.
In my case Rhythmbox needs the Genome libs... and i haven't installed them and really don't want too.
C has, what, 3 over it's 40 years of history?
And yet there is still a sizable code base in this "standard" C that won't compile for a 64bit CPU. And not just any 64bit CPU, but one thats so bloody close to the 32bit version that it supports both modes/instruction/register whatever.
So, in the end, unless we programmers get together and create our own suite of languages..
It would be the worst language of all time. Some ugly cross between python, java, and perl. if else would use 3 different spellings, typing would be optional and the C programmers will insist on direct access to pointers (and hence require an explicit known memory layout for most types) and require (void*) casts everywhere. Because of its total nastiness the compilers would be unable to do any escape analysis and other optimizations would be difficult too. Then the "C" coders will insist that to write fast code you need asm blocks and its all down the toilet. I haven't even got to namespaces, module systems, macros and linking conventions yet.
Java on the desktop is dead.
I think you missed a memo.
Despite what a lot of people think. The games market on PC/servers etc is pretty small. Sun was wise not to push it really. For games you would need Xbox..etc to support a jvm for it to really make sense. And that will not happen for a number of reasons.
....)
However there is lwjgl (opengl/openal binding for java), and most common higher level languages can run on top of a JVM these days. (Jython, JScheme, Kawa, lua,
I believe there is already an eclipse plugin for that ;)
And the openJDK will mean that Oracle ability to shaft it will be limited. Java will remain relevant just like C will.
h.264 is not open. Sure you can read it, but if you code it up and then run that code, or give that code to others, you are breaking the law in a number of countries.
Perhaps reading the h.264 spec is enough for you... But open to me means open to use freely ie without cash or contract.