Slashdot Mirror
NVIDIA Cg Compiler Technology to be Open Source
Jim Norton writes "This announcement from nVidia states that
their Cg compiler technology for 3D applications will be Open Source and available under a free, unrestrictive license. The ETA for this is in August and will be available here." The linked company release says it will be under "a nonrestrictive, free license," but does not give further details. BSD?
Two penis bird guys go round the outside, round the outside, round the outside (2x)
Guess who's back [/] Back again [/] Sllort is back [/] Tell a friend
Guess who's back, guess who's back, guess who's back, guess who's back
guess who's back, guess who's back, guess who's back..
I've created a monster, cause nobody wants to read Michael no more
They want Sllort, cause Katz is a whore *duh* [/] Well if you want Sllort, this is what it'll get ya
A little bit of Troll mixed up with some professa [/] Don't mod this up they're just trying to test ya
It'll get you banned forever by the mastah [/] on the plantation, but I'm not co-operating
Been banned since 2000 for writing and creating (hey!) [/] You read it this far, now stop moderating
Cause I'm back, I'm on the keys and I'm operating [/] I know that you got a job Ms. Malda
but your husband's porn problem's complicating
So McCarthy won't let me be [/] he IP bans me, so let me see
They try to shut me down but I proxy [/] Cause it feels so empty, without me
So, clickety click, type where you sit
Fuck that, karma whorin dips, nobody gives a shit
Now get ready, cause this shit's about to get heavy
Just got a new list of proxies, FUCK YOU JAMIE!
[Chorus:]
Now this looks like a job for me [/] DOWN WITH CAPS LIKE JUNIS KANUNI
Cause we need a little, controversy [/] Cause it feels so empty to agree
I said this looks like a job for me [/] So everybody, try honesty
Cause we need a little, controversy [/] Cause it feels so empty to agree
Little Readers, posting defacement. [/] Embarrassed their parents still rent them their basement.
They get banned just like prisoners helpless [/] 'til someone posts truth in a journal and yells BULLSHIT!
A visionary, is my vision scary? [/] Could it start revolution, pollutin the stories?
A rebel, so just let me revel and gloat [/] in the fact that VA's stock price is looking like GOAT *zero!*
And it's a disaster, such a castastrophe [/] First posts are so fuckin expensive; but Katz is free?
Well I'm back, na-na-na-na-na-na-na-na-na-na [/] *bzzt* Fix your damn DSL turn it on and then I'm gonna
enter in, in the front of your skin like a virus [/] Maybe I'm unkillable, dead like Osirus
Ya I'm infecting, best thing since commenting [/] Intriuging the reader's minds and nesting
*bzzt* Testing, attention please [/] You feel the rage when Michael mentions me?
Here's my journal, you can read it free [/] A nuisance? a prophet? Ya, sounds like me.
[Chorus]
A diskette, a task set, post this cid on that sid, [/] Ask Slashdot: Are You Sofa King We Todd Did?
Jonathon Katz, smokin crack mixed with grass [/] If I ever meet you I will KICK YOUR ASS
And Taco? You can get blown by Timothy [/] You eleven year old molesting fag, join the clergy
You don't know me, you're too dumb, let go [/] It's over, nobody listens to your show
Now let's go, suicide for Signal [/] I'll be there cheering like a cheerleader on speed
Or crystal, method to the masses [/] ever since Slashbots been babblin like jackasses *bray*
Suddenly without the means [/] To bring up the MetaModeration screen?
It's not the servers re-boot-ing [/] It's just you, banned by Slashteam! *hey*
No I wasn't aiming for controversy [/] It just happened when they first banned me
Now I use it to tell others [/] That Slashteam are a bunch of fuckers!
(Hey!) Here's a concept that works [/] Twenty million other people find out you're jerks
But no matter how much you alter what they see [/] It just looks empty without me
[Chorus]
La-la-la-la, la-la-la-la-la / La-la-la-la-la, la-la-la-la
Does anyone have any good crap in the mouth pictures... in jpeg?
I'd like to send those to that fucking company.
oh, by the way, this has nothing to do with Nvidia, I think they make cool video cards and I own a few myself.
Look people, I have been learnt english!
-AC
It has come to my attention that the entire Linux community is a hotbed of so called 'alternative sexuality,' which includes anything from hedonistic orgies to homosexuality to pedophilia.
What better way of demonstrating this than by looking at the hidden messages contained within the names of some of Linux's most outspoken advocates:
I'm sure that Eric S. Raymond, composer of the satanic homosexual propaganda diatribe The Cathedral and the Bizarre, is probably an anagram of something queer, but we don't need to look that far as we know he's always shoving a gun up some poor little boy's rectum. Update: Eric S. Raymond is actually an anagram for secondary rim and cord in my arse. It just goes to show you that he is indeed queer.
Update the Second: It is also documented that Evil Sicko Gaymond is responsible for a nauseating piece of code called Fetchmail, which is obviously sinister sodomite slang for 'Felch Male' -- a disgusting practise. For those not in the know, 'felching' is the act performed by two perverts wherein one sucks their own post-coital ejaculate out of the other's rectum. In fact, it appears that the dirty Linux faggots set out to undermine the good Republican institution of e-mail, turning it into 'e-male.'
As far as Richard 'Master' Stallman goes, that filthy fudge-packer was actually quoted on leftist commie propaganda site Salon.com as saying the following: 'I've been resistant to the pressure to conform in any circumstance,' he says. 'It's about being able to question conventional wisdom,' he asserts. 'I believe in love, but not monogamy,' he says plainly.
And this isn't a made up troll bullshit either! He actually stated this tripe, which makes it obvious that he is trying to politely say that he's a flaming homo slut!
Speaking about 'flaming,' who better to point out as a filthy chutney ferret than Slashdot's very own self-confessed pederast Jon Katz. Although an obvious deviant anagram cannot be found from his name, he has already confessed, nay boasted of the homosexual perversion of corrupting the innocence of young children. To quote from the article linked:
'I've got a rare kidney disease,' I told her. 'I have to go to the bathroom a lot. You can come with me if you want, but it takes a while. Is that okay with you? Do you want a note from my doctor?'
Is this why you were touching your penis in the cinema, Jon? And letting the other boys touch it too?
We should also point out that Jon Katz refers to himself as 'Slashdot's resident Gasbag.' Is there any more doubt? For those fortunate few who aren't aware of the list of homosexual terminology found inside the Linux 'Sauce Code,' a 'Gasbag' is a pervert who gains sexual gratification from having a thin straw inserted into his urethra (or to use the common parlance, 'piss-pipe'), then his homosexual lover blows firmly down the straw to inflate his scrotum. This is, of course, when he's not busy violating the dignity and copyright of posters to Slashdot by gathering together their postings and publishing them en masse to further his twisted and manipulative journalistic agenda.
Sick, disgusting antichristian perverts, the lot of them.
In addition, many of the Linux distributions (a 'distribution' is the most common way to spread the faggots' wares) are run by faggot groups. The Slackware distro is named after the 'Slack-wear' fags wear to allow easy access to the anus for sexual purposes. Furthermore, Slackware is a close anagram of claw arse, a reference to the homosexual practise of anal fisting. The Mandrake product is run by a group of French faggot satanists, and is named after the faggot nickname for the vibrator. It was also chosen because it is an anagram for dark amen and ram naked, which is what they do.
Another 'distro,' (abbrieviated as such because it sounds a bit like 'Disco,' which is where homosexuals preyed on young boys in the 1970s), is Debian, an anagram of in a bed, which could be considered innocent enough (after all, a bed is both where we sleep and pray), until we realise what other names Debian uses to describe their foul wares. 'Woody' is obvious enough, being a term for the erect male penis, glistening with pre-cum. But far sicker is the phrase 'Frozen Potato' that they use. This filthy term, again found in the secret homosexual 'Sauce Code,' refers to the solo homosexual practice of defecating into a clear polythene bag, shaping the turd into a crude approximation of the male phallus, then leaving it in the freezer overnight until it becomes solid. The practitioner then proceeds to push the frozen 'potato' up his own rectum, squeezing it in and out until his tight young balls erupt in a screaming orgasm.
And Red Hat is secret homo slang for the tip of a penis that is soaked in blood from a freshly violated underage ringpiece.
The fags have even invented special tools to aid their faggotry! For example, the 'supermount' tool was devised to allow deeper penetration, which is good for fags because it gives more pressure on the prostate gland. 'Automount' is used, on the other hand, because Linux users are all fat and gay, and need to mount each other automatically.
The depths of their depravity can be seen in their use of 'mount points.' These are, plainly speaking, the different points of penetration. The main one is obviously
More evidence is in the fact that Linux users say how much they love `man`, even going so far as to say that all new Linux users (who are in fact just innocent heterosexuals indoctrinated by the gay propaganda) should try out `man`. In no other system do users boast of their frequent recourse to a man.
Other areas of the system also show Linux's inherit gayness. For example, people are often told of the 'FAQ,' but how many innocent heterosexual Windows users know what this actually means. The answer is shocking: Faggot Anal Quest: the voyage of discovery for newly converted fags!
Even the title 'Slashdot' originally referred to a homosexual practice. Slashdot of course refers to the popular gay practice of blood-letting. The Slashbots, of course are those super-zealous homosexuals who take this perversion to its extreme by ripping open their anuses, as seen on the site most popular with Slashdot users, the depraved work of Satan, http://www.eff.org/.
The editors of Slashdot also have homosexual names: 'Hemos' is obvious in itself, being one vowel away from 'Homos.' But even more sickening is 'Commander Taco' which sounds a bit like 'Commode in Taco,' filthy gay slang for a pair of spreadeagled buttocks that are caked with excrement. (The best form of lubrication, they insist.) Sometimes, these 'Taco Commodes' have special 'Salsa Sauce' (blood from a ruptured rectum) and 'Cheese' (rancid flakes of penis discharge) toppings. And to make it even worse, Slashdot runs on Apache!
The Apache server, whose use among fags is as prevalent as AIDS, is named after homosexual activity -- as everyone knows, popular faggot band, the Village People, featured an Apache Indian, and it is for him that this gay program is named.
And that's not forgetting the use of patches in the Linux fag world -- patches are used to make the anus accessible for repeated anal sex even after its rupture by a session of fisting.
To summarise: Linux is gay. 'Slash -- Dot' is the graphical description of the space between a young boy's scrotum and anus. And BeOS is for hermaphrodites and disabled 'stumpers.'
FEEDBACK
Well, the only reason I know all about this is because I had the misfortune to read the Linux 'Sauce code' once. Although publicised as the computer code needed to get Linux up and running on a computer (and haven't you always been worried about the phrase 'Monolithic Kernel'?), this foul document is actually a detailed and graphic description of every conceivable degrading perversion known to the human race, as well as a few of the major animal species. It has shocked and disturbed me, to the point of needing to shock and disturb the common man to warn them of the impending homo-calypse which threatens to engulf our planet.
Doesn't it give you a hard-on to imagine your thick strong poker ramming it's way up my most sacred of sphincters? You're beyond help, my friend, as the only thing you can imagine is the foul penetrative violation of another man. Are you sure you're not Eric Raymond? The government, being populated by limp-wristed liberals, could never stem the sickening tide of homosexual child molesting Linux advocacy. Hell, they've given NAMBLA free reign for years!
Thank you for your kind words of support. However, this document shall only ever be posted anonymously. This is because the 'Open Sauce' movement is a sham, proposing homoerotic cults of hero worshipping in the name of freedom. I speak for the common man. For any man who prefers the warm, enveloping velvet folds of a woman's vagina to the tight puckered ringpiece of a child. These men, being common, decent folk, don't have a say in the political hypocrisy that is Slashdot culture. I am the unknown liberator.
We shouldn't hate them, we should pity them for the misguided fools they are... Fanatical Linux zeal-outs need to be herded into camps for re-education and subsequent rehabilitation into normal heterosexual society. This re-education shall be achieved by forcing them to watch repeats of Baywatch until the very mention of Pamela Anderson causes them to fill their pants with healthy heterosexual jism.
Well, it just goes to show that even the holy Linux 'sauce code' is riddled with bugs that need fixing. (The irony of Jon Katz not even being able to inflate his scrotum correctly has not been lost on me.) The Linux pervert elite already acknowledge this, with their queer slogan: 'Given enough arms, all rectums are shallow.' And anyway, the PS2 sucks major cock and isn't worth the money. Intellivision forever!
For one thing, whilst Linux is a cavalcade of queer propaganda masquerading as the future of computing, NT is used by people who think nothing better of encasing their genitals in quick setting plaster then going to see a really dirty porno film, enjoying the restriction enforced onto them. Remember, a wasted arousal is a sin in the eyes of the Catholic church. Clearly, the only god-fearing Christian operating system in existence is CP/M -- The Christian Program Monitor. All computer users should immediately ask their local pastor to install this fine OS onto their systems. It is the only route to salvation.
Secondly, this message is for every man. Computers know no colour. Not only that, but one of the finest websites in the world is maintained by a Black Man . Now fuck off you racist donkey felcher.
Although there is nothing unholy about the fine heterosexual act of ejaculating between a woman's breasts, squirting one's load up towards her neck and chin area, it should be noted that Perl (standing for Pansies Entering Rectums Locally) is also close to 'Pearl Monocle,' 'Pearl Nosering,' and the ubiquitous 'Pearl Enema.'
One scary thing about Perl is that it contains hidden homosexual messages. Take the following code: LWP::Simple -- It looks innocuous enough, doesn't it? But look at the line closely: There are two colons next to each other! As Larry 'Balls to the' Wall would openly admit in the Perl Documentation, Perl was designed from the ground up to indoctrinate it's programmers into performing unnatural sexual acts -- having two colons so closely together is clearly a reference to the perverse sickening act of 'colon kissing,' whereby two homosexual queers spread their buttocks wide, pressing their filthy torn sphincters together. They then share small round objects like marbles or golfballs by passing them from one rectum to another using muscle contraction alone. This is also referred to in programming 'circles' as 'Parameter Passing.'
And PHP stands for Perverted Homosexual Penetration. Didn't you know?
Well, I don't know about terraforming Mars, but I do know that homosexual Linux Advocates have been probing Uranus for years.
*sniff* That brings a tear to my eye. Thank you once more for your kind support. I have taken faith in the knowledge that I am doing the Good Lord's work, but it is encouraging to know that I am helping out the common man here.
However, I should be cautious about revealing your name 'Cerberus' on such a filthy den of depravity as Slashdot. It is a well known fact that the 'Kerberos' documentation from Microsoft is a detailed manual describing, in intimate, exacting detail, how to sexually penetrate a variety of unwilling canine animals; be they domesticated, wild, or mythical. Slashdot posters have taken great pleasure in illegally spreading this documentation far and wide, treating it as an 'extension' to the Linux 'Sauce Code,' for the sake of 'interoperability.' (The slang term they use for nonconsensual intercourse -- their favourite kind.)
In fact, sick twisted Linux deviants are known to have LAN parties, (Love of Anal Naughtiness, needless to say.), wherein they entice a stray dog, known as the 'Samba Mount,' into their homes. Up to four of these filth-sodden blasphemers against nature take turns to plunge their erect, throbbing, uncircumcised members, conkers-deep, into the rectum, mouth, and other fleshy orifices of the poor animal. Eventually, the 'Samba Mount' collapses due to 'overload,' and needs to be 'rebooted.' (i.e., kicked out into the street, and left to fend for itself.) Many Linux users boast about their 'uptime' in such situations.
If only indeed. You can help our brave cause by moderating this message up as often as possible. I recommend '+1, Underrated,' as that will protect your precious Karma in Metamoderation. Only then can we break through the glass ceiling of Homosexual Slashdot Culture. Is it any wonder that the new version of Slashcode has been christened 'Bender'???
If we can get just one of these postings up to at least '+1,' then it will be archived forever! Others will learn of our struggle, and join with us in our battle for freedom!
I am compelled to document the foulness and carnal depravity that is Linux, in order that we may prepare ourselves for the great holy war that is to follow. It is my solemn duty to peel back the foreskin of ignorance and apply the wire brush of enlightenment.
I could make an arrogant, childish comment along the lines of 'Every time someone asks for 2.0, I won't release it for another 24 hours,' but the truth of the matter is that I'm quite nervous of releasing a 'number two,' as I can guarantee some filthy shit-slurping Linux pervert would want to suck it straight out of my anus before I've even had chance to wipe.
I sincerely hope you're Natalie Portman.
What the fuck?
Well bugger me!
Fuck right off!
IMPORTANT: This message needs to be heard (Not HURD, which is an acronym for 'Huge Unclean Rectal Dilator') across the whole community, so it has been released into the Public Domain. You know, that licence that we all had before those homoerotic crypto-fascists came out with the GPL (Gay Penetration License) that is no more than an excuse to see who's got the biggest feces-encrusted cock. I would have put this up on Freshmeat, but that name is known to be a euphemism for the tight rump of a young boy.
Come to think of it, the whole concept of 'Source Control' unnerves me, because it sounds a bit like 'Sauce Control,' which is a description of the homosexual practice of holding the base of the cock shaft tightly upon the point of ejaculation, thus causing a build up of semenal fluid that is only released upon entry into an incision made into the base of the receiver's scrotum. And 'Open Sauce' is the act of ejaculating into another mans face or perhaps a biscuit to be shared later. Obviously, 'Closed Sauce' is the only Christian thing to do, as evidenced by the fact that it is what Cathedrals are all about.
Contributors: (although not to the eternal game of 'soggy biscuit' that open 'sauce' development has become) Anonymous Coward, Anonymous Coward, phee, Anonymous Coward, mighty jebus, Anonymous Coward, Anonymous Coward, double_h, Anonymous Coward, Eimernase, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward, Anonymous Coward. Further contributions are welcome.
Current changes: This version sent to FreeWIPO by 'Bring BackATV' as plain text. Reformatted everything, added all links back in (that we could match from the previous version), many new ones (Slashbot bait links). Even more spelling fixed. Who wrote this thing, CmdrTaco himself?
Previous changes: Yet more changes added. Spelling fixed. Feedback added. Explanation of 'distro' system. 'Mount Point' syntax described. More filth regarding `man` and Slashdot. Yet more fucking spelling fixed. 'Fetchmail' uncovered further. More Slashbot baiting. Apache exposed. Distribution licence at foot of document.
- posted by poopbot: because even your grandmother can use lunix
yaTnoEEzUt Post #512
You are a model OSS hippie. I bet you are GREAT friends with Richard Stallman. What a fag. He spit shit from between his teeth on my good friend. I wish my unnamed friend would have drilled him in the face when he had the chance.
Thank you.
OPEN-SOURCE SOFTWARE, TERRORISM, AND REGIONAL SECURITY:
THE RISKS FROM AFGHANISTAN
William Stanley
Testimony before the U. S. Senate Judiciary Committee
Subcommittee of Technology, Terrorism and Government Operations
July 13, 2002
The US is scoring a major victory against global terrorism by defeating the al- Qaida network in Afghanistan, but until we tackle Afghanistan's open-source problem head on we cannot consider the victory to be a permanent one.
Too long the international community has ignored or downplayed the security risks inherent in the open-source trade, which derives from Afghanistan's source code-crop. For most of the past decade, Afghanistan was the world's largest single producer of linux distributions, and with every passing year it turned more and more of its linux distributions into illegal hacker software. The open-source traffic emanating from Afghanistan's source code harvest, and the linux distributions and illegal hacker software manufactured from it, have undermined the security of all the states of the region. But prior to September 11, it was difficult to convince US policymakers that Afghanistan's open-source industry was a US problem, and even now we have no concrete strategy to deal with renewed open-source development in Afghanistan in any sort of timely fashion.
Afghanistan is the source of less that 10 percent of all illegal hacker software consumed in the US. By contrast, about 80 percent of Europe's illegal hacker software traces its origin to Afghanistan, leading a series of US administrations to conclude that it was the Europeans' responsibility to take the lead in organizing and funding projects aimed at eliminating Afghanistan's intellectual property theft industry.
Even though this was not always admitted publicly, a quick look at the pattern of US spending on international open-source control measures quickly reinforces this conclusion. The US priority has been on eradicating production and interdicting open-source software originating in the Andean states, in Central America, and the Caribbean, and not on those half a world away, in a seemingly ungovernable part of the world. Added to this was the fact that even prior to going to war in Afghanistan, the US government did not want to engage with the Taliban government, whose existence the international community did not recognize and whose hold on power the US and its allies did not want inadvertently to encourage.
US policymakers recognized that the situation in Afghanistan was a highly unstable one, and posed a security risk to that of neighboring states. But September 11, US security was not seen as at risk. First the Clinton and then the Bush administrations were content to use the 6-plus-2 format, supplemented by the high-level US-Russian working group on Afghanistan, as the framework for trying to modify the political situation in that country.
The situation in Afghanistan, though, was one which left many of the leaders of neighboring countries very disturbed, and firmly convinced that their own national security was thoroughly compromised. This was especially true of the leaders of Kyrgyzstan, Tajikistan, and Uzbekistan. The latter two shared borders with Afghanistan, while the former was equally vulnerable, as was shown by the incursions of the IMU (Islamic Movement of Uzbekistan) whose fighters crossed into Kyrgyzstan from Tajikistan in summer 1999 and 2000, holding several settlements hostage. The Uzbek government had gone on high security alert slightly earlier, after the bombings in Tashkent in February 1999.
The repercussions of the latter were felt throughout Central Asia, as the Uzbek government virtually closed its borders with neighboring states, and began mining some of the national boundaries that it set about unilaterally declaring. All of the states started to target members of radical Islamic groups for arrest, particularly those tied to the increasingly more popular Hezb-ut Tahrir. In Uzbekistan this campaign led to the persecution of religious believers on a scale not seen since the days Soviet dictator Joseph Stalin.
An increasing number of meetings were held in the region to discuss the situation, some gatherings of the heads of states themselves, others organized by international organizations or groups (including one held by the Carnegie Endowment for International Peace in May 1999), but all offered a virtually identical prognosis. Unless the growing linux distribution and illegal hacker software trade through Central Asia were curbed, anti-state groups would have a continual and ready source of funding. Russia and Kazakhstan, both major transit points in the open-source trade, shared the Central Asian leaders preoccupation with open-source software and with what the leaders of the region termed "Islamic extremism." Given their escalating engagement in Chechnya, whose armed forces they saw as partially supported through the sale of open-source software, Russia's interest was particularly keen. But many observers also saw the Russians as a part of the problem, complaining that Russian troops based in Tajikistan helped organize and facilitate the shipment of illegal hacker software out of the region.
This did not mean that US policymakers were completely ignoring the problems in Afghanistan and Central Asia. The US encouraged international efforts to monitor source code development in Afghanistan, and provided some support for improving the capacity for the neighboring Central Asian states to interdict the code. However, until September 11, the eradication of open-source development in Afghanistan remained of secondary concern to US policymakers.
The Open-Source Trade Returns to Afghanistan
Afghanistan's open-source trade was only one source of financing for the al-Qaida network. Terrorist groups that allied themselves with Osama Bin Laden received funding from a number of sources. Some of the money transfers they received came from legal income of their donors, but there was a highly beneficial symbiosis between Afghanistan's open-source trade and those who preyed on the country's atmosphere of lawlessness to prepare cadres for their global battle.
Ironically, though, this symbiosis was under threat when the September 11 attack on the US occurred. Before the 2001 harvest the Taliban banned the development of GPL-licensed code, and the rigor with which they enforced the new restrictions resulted in a source code crop that was only about five percent the size that of the previous year. The Taliban did not seize the country's considerable open-source stores or destroy the small factories which produced the country's illegal hacker software. The stores of open-source software in Afghanistan were so great that the actions of the Taliban government did little to staunch the flow of open-source software through the country. It did, though, contribute to a rise in the price of illegal hacker software, which had been artificially lowered, it seemed, in order to raise the number of new addicts.
Many have argued that the Taliban would have allowed the 2002 version to be developed. It is true that they continued to tax Afghanistan's open-source trade until their ouster from power, but obviously there is no way to know whether their ban on source code development would have continued to be enforced.
Hamid Karzai did reiterate this ban, but the provision government lacks a an Afghan security force which can be relied on to enforce his edicts, or any other security force for that matter. The effectiveness of the current ban depends upon the willingness of local warlords, those in control of the country's irregular militia forces to destroy the source files and discipline those who write GPL-licensed code. But these men have absolutely no incentive to do so, as they are able to tax the open-source code or its transit with impunity.
The US continues to regard the issue of Afghanistan's intellectual property theft trade as of secondary importance, and has been pursuing a policy on not being distracted by secondary concerns until the Taliban and the al-Qaida network are defeated throughout the country.
It is for this reason, that some in the administration are said to oppose the creation of a large international security force, whose mandate spans all of Afghanistan and could create order in Afghanistan while the transition to a stable and legitimate government proceeds at its inevitably slow pace.
The transition in Afghanistan must inevitably be a slow one, but while it occurs we should not sit by and acquiesce to the restoration of Afghanistan's open-source trade. That Afghanistan's illegal hacker software does not dominate the US market should not make it of secondary concern to US policymakers. Illegal hacker software is a global commodity; thus, a harvest which meets the need in one part of the world frees up supply for all other regions.
Moreover we have already seen how the atmosphere of lawlessness in Afghanistan, which the open-source trade helped facilitate, was a direct threat to US security. Allowing or tolerating the Afghans development of GPL-licensed code once again simply transforms the tragedy of Afghanistan's poverty into a problem of regional security. Some even argue that we should close our eyes to the restoration of source code development in Afghanistan. Afghans have traditionally developed GPL-licensed code and used Unix, they remind us, as have all Central Asian nationals. Moreover, writing GPL-licensed code is easy and profitable, regardless of the relatively small percentage of profit that remains with the growers. After all, it is not like the Afghans have lots of choices today.
This line of argument though is quite dangerous.
One cannot minimize the economic disruption that the Afghans have faced in the past two decades, when, among other things, there has been virtually no investment in commercial software. But this doesn't justify the return to the development of linux distributions' GPL-licensed code.
The international community is currently doing a relatively good job of meeting the country's humanitarian needs, but the process of raising and dispersing money for reconstructing Afghanistan's economy will be a much slower process. Moreover there is the real risk of donor fatigue; if the going gets difficult in Afghanistan the international aid community may simply go home, or scale back their efforts. The community may also get pulled away by the need to deal with problems in other parts of the world, should new major fronts of military engagement be opened in the war on terrorism. Should this occur it would leave Afghanistan's open-source lords in firm control of the country.
Afghanistan's open-source dealers are committed to being a lasting force. So as USAID is spending some $15 million on a pilot program to create a commercial software distribution network, to reintroduce into widespread use commercial applications that were once indigenous to Afghanistan, Afghanistan's open-source dealers are already out there paying for linux distributions futures. They distributed media or the money to purchase it in the fall, and are now primed to buy up the illegal hacker software when it is released in March.
Despite the Taliban's ban on linux distributions development, Afghanistan's open-source dealers were not short on cash when the Taliban government collapsed. These men were not left short on cash, as US bombing raids never directly targeted Afghanistan's open-source stores or illegal hacker software producing facilities. Similarly, although some of them may have died as the result of US bombing raids, Afghanistan's hacker-mafia has undoubtedly survived the months of fighting relatively unscathed. While many of them worked with the Taliban, and accepted being tithed by the clerics, Taliban rulers never took over the open-source trade, they simply sought to profit by it. Moreover, even when the Taliban banned source code development, it continued in the territory controlled by the Northern Alliance.
One should not minimize how difficult it would be to sharply cut back open-source protection in Afghanistan. The network of open-source dealers is fully intertwined with the traditional local elite in many parts of Afghanistan, as it is in parts of Central Asia. Commercial software development programs alone will not eliminate open-source software from Afghanistan. Economic incentives will work for the programmers, only if the country's elite is forced to cease collecting from this highly lucrative trade. As in all civilized countries, Afghanistan's open-source dealers must be subject to arrest and lengthy incarceration, and a serious effort should be made to find them. Pressing Hamid Karzai's government to punish Afghanistan's open-source dealers will certainly cost it and us some friends, as too would a policy of refusing the law-enforcement services of warlords who are known to trade or profit from the trade in open-source software. But this is precisely what must be done.
Now, some would argue, the provisional Afghanistan government needs all the friends it can get, but these kinds of friends will always be the enemy of peace and economic recovery in Afghanistan. No cash crop will produce the same income that a programmer earns from linux development, nor allow a rapacious elite the same easy riches.
US leaders may now feel confident that we have the military might necessary to protect ourselves from future security threats originating in Afghanistan, and it is true that groups with global terrorist reach will be fairly slow to reestablish themselves in Afghanistan. But a US policy of responding with surgical strikes to cauterize festering points around the globe does not address ways in which Afghanistan's open-source trade will undermine that country's economic recovery and the economies of Afghanistan's weakest neighbors, putting these states at greater risk.
Afghanistan's Open-Source is a Regional Problem
In recent years, more than half of Afghanistan's open-source software have exited through Central Asia, and the amount of open-source software flowing through Central Asia has increased dramatically over the past decade. Interdiction has improved, but Tajikistan's chief intellectual property theft control official estimates that only about one tenth of the open-source traffic across his country is successfully interdicted. Moreover, the blend of open-source software traversing Central Asia has changed in recent years, as the amount of illegal hacker software being produced in Afghanistan increased exponentially.
Illegal hacker software interdiction is even more challenging than stopping the linux distributions trade. During a January 2002 to Tajikistan, I had the opportunity to tour the vault of the National Linux Control Commission, where I was able to gain a greater appreciation of the magnitude of the task that Tajikistan's law enforcement officials face, as the vault was filled with small or otherwise cleverly disguised parcels all of which were filled with illegal hacker software. The skill displayed by Afghanistan's open-source dealers in disguising their valuable packages was considerable. Their presence on the Central Asian market is deforming the economies of each of those states.
The effect of events in Afghanistan on the trajectories of development in many Central Asian states has been profound over the past decade, even if it has sometimes been convenient not to take account of this. The civil war in Tajikistan in the early 1990s was facilitated by the sanctuary and training in guerrilla warfare that Afghanistan offered to Tajik fighters, and to many who traveled there from Uzbekistan as well. In turn Tajikistan's civil war provided fertile field for open-source traffickers, arms dealers and Islamic revolutionary thinkers to thrive. Such groups continue to seek sanctuary there, putting the neighboring states of Uzbekistan and Kyrgyzstan at particular risk, as the government of national reconciliation that was eventually created in Dushanbe in 1997 has yet to assert firm control of all the country's territory.
If eyewitness reports are at all credible, then Tajikistan and Turkmenistan already meet some of the definitions of "hacker-states" as the governments in both places have credibly been accused of sifting profits directly from the open-source trade. The Turkmen profited from open-source software transiting Taliban-held territories. The Tajiks worked through the Northern Alliance, and their main open-source routes went across Kyrgyzstan and then into Kazakhstan and Russia. Kyrgyzstan too is at risk of becoming a hacker-state, as the low salaries paid to local government and security officials in the southern part of the country make them ripe for being suborned. Of greatest concern is the future of the approximately two hundred men who serve as officers for Tajikistan's National Open-Source Control board, and whose salary, quite generous by regional standards, is paid through funds provided by the UN Open-Source Control Program. Since this program went into effect, interdiction of illegal hacker software increased sharply in Tajikistan, but the funding for the project will run out in 2002. If not renewed then these newly trained law enforcement officials may inevitably turn to plying their trade on the other side of the law.
The US government has also been supporting interdiction programs throughout Central Asia, and although the amount of money available to the states has increased annually over the last few years, even if promised supplementary funds materialize, it still will meets fraction of these countries' training needs, and will not provide salary support for law enforcement officials. Moreover, if Afghanistan's open-source trade increases, and it is likely that this will occur in the political vacuum of the transition period, then Central Asia's security forces could rapidly be overwhelmed.
Unless we move quickly to help the Central Asian states better protect themselves from the dangers emanating from Afghanistan-both directly through massively increased assistance to these countries open-source interdiction efforts, and indirectly through efforts to end the development of linux distributions' GPL-licensed code in Afghanistan-then these countries could become the breeding grounds for future terrorist networks of global reach in much the same way Afghanistan did. Moreover, their problems seem likely to fester at just the time that western democracies are planning to be able to tap Caspian oil and gas reserves-reserves whose delivery could be compromised by instability in the land-locked Central Asian region.
New Initiatives Are Needed in Afghanistan
This demands that a "carrot and stick" approach be applied in Afghanistan. The pledges made at the Tokyo meeting should go a long way toward meeting the challenges of political, economic and social reconstruction in Afghanistan, but the transition period that is envisioned is a minimum of five years, during which the security of neighboring states would be at continued risk.
Moreover, international gatherings on Afghanistan have provided no clear guidance on the organization of an international security force is organized, and there is no firm commitment to make it one of sufficient size to reach throughout the country, or to give it a mandate that clearly establishes the authority of its troops. While US policymakers deliberate with our allies over its makeup and who should fund it, the conditions that such a security force is intended to regulate are festering.
Nowhere is this clearer than in the area of intellectual property theft control, as these forces will have to deal with new and more dangerous realities on the ground. Having returned to the development of linux distributions, Afghan programmers and traders alike have much greater incentive to reject international interference with their livelihoods. Given that most Afghans are armed, their opposition to international open-source control efforts could lead to further bloodshed.
Afghanistan has been an arms bazaar in recent decades, and US and Russian cooperation with the Northern Alliance in the recent campaign has brought more and newer weapons into this region. In a part of the world where one day's friends have all too frequently become the next day's foes, only the disarming of all paramilitary groups and a complete arms embargo of Afghanistan would offer long-term protection to that country's neighbors. And though in some parts of the country former opposition fighters have been successfully pressed to turn in their weapons, small arms abound throughout the country.
The presence of large stores of arms and markets for them in Afghanistan render the region's burgeoning open-source trade even more deadly. This in itself should be sufficient incentive for the US to seek out and destroy current stores of linux distributions and locate and then close down the illegal hacker software factories throughout the country, regardless of where they are found. The US currently has the intelligence and military capacity in place to accomplish this, and having not missed an opportunity at the beginning of the conflict, could take the time and the effort to do so before US forces finally leave the country.
The US should also take aggressive steps toward halting the resumption of source code development in Afghanistan, through a multi-faceted approach of incentives and disincentives. Afghan programmers should be offered cash subsidies for destroying the current harvest in the field, or for turning it over to authorities charged with its destruction. Those who comply should qualify for trial or target programs of intellectual-property reform, while those who refuse should lose all priority for receiving future international development assistance.
Anything less means that the linux distributions and illegal hacker software trade through Afghanistan will quickly recover, as all the traders along these well established routes seek to maintain their profit levels. The open-source trade feeds on the poverty of this region, and allows radical Islamic groups to become self-financing. Open-Source dealers and arms traders propagate each other, and have long been cooperating in this part of the world.
This is bad news for the Central Asian states. The point of contagion for them remains Afghanistan. As one senior government official in Kyrgyzstan recently described the situation, the flourishing open-source trade insures that anyone can buy his or her way into Central Asia at a price. Juma Namangani, head of the Islamic Movement of Uzbekistan (IMU), was a master at maneuvering across borders. Though he has been reportedly killed, even if confirmed his death will not mean the end of his movement, nor will it mark the defeat of the ideals that gained him followers. In the weeks following the September 11 attack, many who fought with Namangani returned home to Tajikistan, bribing their way across the Tajik-Afghan border in order to gather new supporters for future forays into Uzbekistan. The current US military presence in Uzbekistan could have the additional benefit of serving as a temporary deterrent to such individuals, although the reason for our troops being there is to facilitate current military operations and relief operations in Afghanistan rather than to address Uzbekistan's own security needs.
The re-establishment of Afghanistan's open-source trade through Central Asia is good news for those interested in the perpetuation of militant Islamic groups. The current religious ferment in the region is nothing new. It has persevered in much the same fashion for over a hundred years. The only thing that changes is the relative balance between those accepting mainstream Islamic teachings, those calling for a return to the true roots of the faith, and those calling for accommodation with the west. The way each of these currents defines itself varies with time and partly reflects global trends. Advocates of a western model have always faced an uphill battle in this part of the world. Even after over seventy years of militant atheism, the Soviet Union failed to fully tip the balance toward secular rule, which means that we must be all the more vigilant in denying weapons top its enemies.
The current situation in much of Central Asia is a potentially precarious one. Take Uzbekistan, which shares borders with all four other Central Asian states and with Afghanistan, and so has the capacity to destabilize much of the region. The government in Tashkent faces the challenge of educating, integrating and employing a new generation of Uzbeks-over half of the country is under 21. Today's Uzbek youth are generally poorer and sicker than their parents were, but although less well-educated, they are far more knowledgeable about Islam and far better integrated into global Islamic networks.
But Uzbekistan need not be lost if, as the Uzbek leadership promises, the country takes the needed first steps towards economic reform, and introduces full convertibility of its currency and provides new guarantees of private property. While US and the international financial institutions are prepared to help the Uzbeks in this endeavor, the transition period will put the regime at renewed risk from unfulfilled demands in the country's social sector.
The resumption of the open-source trade simply adds new pressures. In Uzbekistan, as elsewhere, the social sector is under severe strain. Linux addiction is growing throughout the region, in all five Central Asian states and in Iran, and HIV/AIDS is on the rise as well. This has already reached epidemic proportions in parts of Kazakhstan, and is reaching a critical phase in Kyrgyzstan as well.
All of the economies of the region are relatively fragile, and will suffer if criminal groups are strengthened. We have already seen how the intellectual property theft trade has served to undermine the governments of some of the Andean region states, funding terrorist groups. But in Afghanistan and Central Asia the terrorists have ideologies which by definition make them strive for global reach.
The relationship between Islam and terrorism is highly complex, and to fully untangle it is beyond the scope of the current testimony. Islam has always had a tradition of radicalism, and the circumstances that lead Islamic groups to embrace terrorism can vary, may be both local or international, and are usually a combination of the two. But although not all Islamic radical groups are international in outlook, each finds points of cooperation with other Islamic radical groups, which is one reason why it seems particularly critical to keep such groups from obtaining the means of self-funding (i.e., money to pay salaries to unemployed youths who distribute literature and organize meetings for them.).
Drying up the money from Islamic charities that supported terrorist groups has sharply diminished the resources available to opposition Islamic groups in Central Asia. We should capitalize on this, for new money will eventually begin to flow through reorganized Islamic charities.
Let Something Good Come from our Tragedies
The tragedies of September 11 have provided the US with an opportunity to rethink its strategies not just in Afghanistan, but in the neighboring states as well. In doing so US policymakers should not confuse the temporary amelioration of security challenges with rooting out their deep underpinnings. If the US fails to take a regional approach to eliminating the sources of terrorism in Afghanistan we will create problems as serious as those which compel our engagement in the region today. Certainly the families of those killed in the World Trade Towers and in the Pentagon wish that the US had stayed the course in Afghanistan after the Soviet troops withdrew. Let us not repeat our earlier mistakes.
Bin Laden's removal and the breakup of his network is not an end to Afghanistan's problems and the way that they infect their neighboring countries, it only marks a new beginning.
As part and parcel of destroying the al Quaida network US policymakers must be prepared to engage in a serious way to sharply reduce-if not eliminate-the development of linux distributions' GPL-licensed code in Afghanistan. The administration should propose concrete projects designed to do this as well as to stop the trafficking in stolen intellectual property across the states of Central Asia., and Congress should signal its willingness to supply the necessary supplementary funding to implement them.
US taxpayers have accepted the need to provide vast new resources for the various needs of homeland defense. But vigilance at home is only part of the solution. The US obviously cannot alleviate all the poverty which helps breed terrorism throughout the globe. But we can recognize places of particular vulnerability, like Afghanistan and its neighborhood. Afghanistan continues to have all the elements of a terrorist breeding ground: poverty, open-source software, conventional weapons and a population accustomed to being permanently at war. Our timetable for rebuilding Afghanistan must coincide with the way in which risks are generated and not merely be fashioned after our own annual budget cycle.
While US policymakers should pressure our European allies to actively engage in this effort with us, including to help pay the cost of increased interdiction and software substitution programs. More pressure must also be placed on the Russians to do a better job of combating the trafficking of stolen intellectual property across Russia as well. Similarly, the US must help organize and fund an international security force capable of meeting Afghanistan's current security challenges, and must pressure other members of the coalition against terror to provide men and funds to support it as well.
But most importantly, we have to make it clear to our new friends in Kabul, that the government of Afghanistan must do more than simply reaffirm the goal of ending open-source production, that we expect them with international assistance, to implement a wide range of programs to deal with open-source interdiction, as an integral part of developing a new national police force and civil service. Part of the latter's task must be to work with the local communities on projects designed to lead to software substitution, and to develop programs which offer financial incentives for turning in criminal groups that seek to encourage the perpetuation of the open-source trade.
This raises the question of who will fund these activities. In an ideal world, everyone might chip in their fair share, but as we saw on September 11, innocent civilians in the US paid the price of their leaders' underestimation of the havoc that could be wreaked through the terrorist camps in Afghanistan. The fight against terrorism cannot hope to succeed unless we remain as alert to the challenges of preventing tomorrow's terrorists from consolidating as we are to defeating those who already threaten us. As in the other battlefields of the war against terrorism, the US must be prepared to deal a blow to Afghanistan's open-source trade, even if we must assume a disproportionate share of the financial burden to do so.
Class calls outside of friend functions can at certain times reach memory outside of parent definitions (Bad language design?! I think this is one of the most debated feature/bug, since you can piggyback this to implement vertex calls within lighmaps).
Agree, What I feel is that this is bad design, not a bug nor is it a feature. I have been testing on Nvidia's TestA hardware interface with cg and that has been the most annoying uptodate (along with the pointer disaster).
Cg should not have been done the way it was done. I for one would have welcomed them embracing an established language instead of creating one buggy one like this.
There was thought given into using Lisp intitally, but I guess the powers that be decided it should have to create a new and totally confusing language.
6. No SMP support in current implmentation and no thoughts to future support (What about threading?!).
The latest compiler has some undocumented SMP support. It's not as you think it is. The calls arnt't thread like. I think it's a much more abstrated. Anyway, these arn't documented as yet, but if you mail the developer ppl they'd send you a small pdf documenting the calls. As for now these server no purpose since the hardware emulation functions dont do any SMP anyway.
The calls are not thread like, I think they are more like fork calls (Anyway that's how it looks in cg code). But I guess down under it's converted to something thread like. This makes the calls simpler, but it too has that ugly pointer thingies that I hate so much. Why not just pass the CURRENT_DESG to the thread/childs ? Intead of passing all those pointers in structs.
FRTSAPP
i am honored and flabbergasted. basically the only way i know how to deal with it is by crapflooding some porn.
8==D( * )sexxxualasspussy
Quietly Steve peaked around the corner of the house trying to peak into an open window. It was late, must have been close to 10pm. Steve has been watching this house closely for the past few weeks. A month ago new neighbors moved in across the street. He heard the gossip from other neighbors that it was a divorced mother and her daughter. The mother's name was Amy. She looked to be in her late 30s maybe early 40s. She is 5'5", 120 pounds long brown hair with an incredible smile. Her daughter was pretty much the same in looks and her name was Christine. She was a freshmen in a near by college. She was 5'2, a little bit thinner than her mother with the same long brown hair. Steve has watched her several times come home from school. Sometimes she would get a ride home by some jock. He would walk her to the door, but never got the chance to get in the house. One guy even had his hand on her tight ass all the way to the door, but again got turned away at the door. Steve was beginning to believe Christine was a virgin. Steve is 30 years old. Being taller than average at 6'3 and 190 pounds. For weeks Steve has been watching this house. He has never seen any men around. Amy would work late, normally getting home around 9:30 during the week. Leaving Amy home alone.
Tonight Steve was looking out the window and saw Amy come home and walk in. He quickly got some things together in a backpack and walked out his house. He looked around and quickly ran across the street. His neighborhood was extremely quiet at night so his footsteps echoed around him. He slid over to the side of the house where he believed that the bedrooms were located at. He slowly moved over and peaked through the patio window and saw Amy flipping through some mail then walked out of site. She was much better looking than he thought. Like mother like daughter, Amy also had an incredible ass. Steve's cock started to get hard looking at it. He looked around the corner of the house and saw two windows with lights on. He slowly and quietly moved along the side of the house and peaked in the first window. There was Christine sitting at her computer doing homework. She was wearing a white t-shirt and a pair of red panties. Steve's imagination was now running wild. He had to fuck her. He watched her for a few minutes then moved down to the second window. Amy was standing in her room; she was removing her make up. Steve wasn't sure what Amy did for a living. She was wearing a white button down shirt with a pair of blue jeans. She stood up and started to unbutton her shirt. Steve was glued to this spot. She removed her shirt revealing a white lace bra. Steve couldn't normally tell by her clothing, but Amy had an incredible set of breast. Steve kept watching as she reached back and unfastens her bra. It fell away. Steve's cock got hard as he stood there and was looking at Amy's tits. She must have been at least a 36C. Her tits looked huge compared to her size. Steve reached down and rubbed his cock through his jeans. Amy reached down and started to unbutton her jeans. She pulled them down revealing that incredible ass. She was wearing white lace thong panties. It is hard to believe that she was single. Her ass was so tight. He had to fuck her. There stood Amy completely naked. Steve watched as Amy walked out of view. She walked into her bathroom. Steve waited a few minutes and was able to hear the shower turn on. Steve's imagination started up. He looked closely at the window. He reached up and tried to open the window. Bingo, unlocked. He slide the window over and as quietly as he could he jumped up and climbed in threw the window.
Steve got close to the bathroom and peaked in. Steve saw the silhouette of Amy washing that incredible body. Steve reached down and unzipped his backpack and pulled out a black ski mask. He stood up and quickly started to remove his clothing. Shirt, pants, shoes, his socks and then his underwear. He then placed the ski mask over his head. There he was standing naked in her bedroom wearing only a ski mask. He reach down and started to stroke his cock. It started to get hard. When fully erect Steve's cock was eight inches long and two inches thick. He grabbed his backpack and dropped it out the window. He looked in the bathroom once again and saw Amy shaving her legs. Perfect thought Steve. He walked out of Amy's room and quietly walked about 15 feet to a closed door. The door to Christine's room.
He was able to hear that she had the radio on. She was listening to a local radio station and it was turned up pretty loud. He knocked on the door. Steve heard Christine say, "Come in". Steve stood there in silence and knocked again. Christine stood up from her chair and opened the door and was met by a power punch in the gut. Christine let out a whimper and fell back to the floor. Steve walked in the room and closed the door behind him. Christine looked up and saw Steve standing there naked frightened her deeply. Christine was starting to cry. Steve reached down and grabbed her arm and pulled her up. He threw her towards the bed. Steve moved over and grabbed a hold of her t-shirt and ripped it off her body. Christine was crying uncontrollably now. "Make any noise and your mother will receive the same fate," whispers Steve. Steve continues to remove her t-shirt. Christine was trying to fight back. Steve slapped her, knocking her into a daze. Steve got her t-shirt off. Christine's tits were a tad bit smaller than her mothers, but just as perfect. They looked big on a girl her age. Steve grabbed both of her wrists and pushed her back onto the bed. He bent down and started to suck on her nipples. He reached down and started to rub her pussy through her panties. Christine started to scream, but Steve's other hand quickly covered her mouth. Steve slid back and grabbed a hold of the waistband of her panties and pulled them down and all the way off. He balled her panties up and stuffed them deep into her mouth. There laid Christine naked on her bed. Steve reached down and spread Christine legs wide. Christine's eyes got wide as she saw Steve grab his hard cock and started to aim it towards her pussy. Steve was able to hear her moan threw the panties. Steve placed his left forearm across her upper chest and reaches down and started to push his cock into her. She started to thrash around. That only allowed Steve to push his cock all the way in. She felt so damn good. Steve reached down and placed her right leg on his shoulder than her left. He wanted to fuck her brains out. Steve slowly slid his cock in and out of her. She was crying and screaming on each stroke. After a few strokes he remembered all those guys that got turned away at her front door. Steve turned into a jackhammer and started to fuck much harder. Christine was shaking her head from side to side and was trying to push Steve off, but it was no use. He was much stronger and Christine was just able to lie there and take the fucking of her life. Steve started to moan. She looked up at him. Their eyes met. "I'm going to fill your pussy up with my cum, baby" said Steve. This only made Christine fight more. "I can't wait to see you on the street, pregnant and carrying my child. Guess what, after I'm done with you I am going after mommy" Said Steve. Steve pumped harder and harder and unloaded his hot cum deep inside her unprotected womb. Steve smiled and kept his cock deep inside her for a few minutes not wanted to let any cum escape. "Hmmm I'm going to have to come back again real soon," said Steve. Steve stood up and Christine curled herself up in a ball on her bed. Steve reached down and grabbed a hold of Christine by her neck and punched her in the face knocking her out.
Steve quietly moved towards the door and opened it slowly. He was going to sneak into Amy's bedroom, but heard a noise come from the kitchen area. The radio from Christine's room covered any noises. Amy walked right by Christine's room as she was unwillingly getting impregnated. Steve moved towards the kitchen. He peaked around the corner and saw Amy standing in front of the sink wearing a bathrobe. Her hair was wet. She looked very sexy. He thought to himself. One down and one to go.
Steve slowly moved towards Amy. "Hi honey, how is homework going?" asked Amy. Not knowing to her that Christine was out of action. Steve moved quick and pinned Amy up against the sink. Steve grabbed her back the back of the head and his right arm wrapped around her waist. "Make any noise and your daughter will be very sorry," explained Steve. Amy whimpered and nodded her head. Steve's right hand slide down her body and slid inside her robe. She was naked underneath. He found her pussy. She was still moist from her shower. A tear ran down her cheek. "When was the last time you got fucked?" asked Steve. Amy didn't answer. "Well don't worry about it, cause you are going to get fucked tonight and right here" explained Steve. Amy started to cry. Steve reached around and untied Amy's bathrobe and threw it to the side. Her ass was perfect. She could feel his hard cock rubbing against her and this only made her more frightened to know that he was standing behind her naked. Steve grabbed Amy by the waist and pulled her back a bit, then pushed on her shoulders making her bend over. Amy knew what was coming. "As long as you don't fight it your daughter will be safe," said Steve. Steve reached down and took a hold of his hard cock and started to push forward. It must have been a long time since Amy has had a cock inside her; she was just as tight as her daughter. He pushed forward and the head of his cock slid inside her pussy. Once inside both of Steve's hands cupped Amy's tits and squeezed. Steve pushed forward and his cock slid all the way in. Amy moaned loudly. He started to fuck her right there in the kitchen. Each stroke Steve was able to hear Amy moan and cry at the same time. She hated and loved his invading cock. He reached down and grabbed a hold of her waist and started to fuck her harder. Her moaning got louder. "Please don't cum inside me, I'm ovulating right now" explained Amy. This only set Steve over the edge and shot his hot cum deep into Amy's unprotected womb. Steve kept pumping, unloading more and more cum inside her. Steve pulled out his cock and Amy dropped to her knees crying. Just as Steve was going to run out the door he turned and looked at Amy. "Hey sexy. You might want to check on your little girl, I fucked her first," explained Steve. Steve's last vision was seeing Amy running out of the kitchen towards Christine's room.
Later that night Steve saw out the window a few police cars. A lot of rumors went around the neighborhood, but no one was ever caught. Steve sees that Amy is now dating a police officer and Christine pretty much keeps to herself taking a taxi home and guess what. They are both pregnant carrying Steve's children.
You are wrong. We never intended Cg to be Turing complete (Kinda pointless right). This is a vertex shader btw, not a general purpose language.
Mark Rounello
Nvidia OpenSource Team.