January 13th, 2010


Two Fun Filled Posts

Update on Our Brave New Slavery: Yes, It Applies to American Citizens, Too - where we learn that gosh, maybe John Yoo had a majik bullet after all. Since golly,
anyone who is arbitrarily declared a "suspected enemy combatant" by the president or his designated minions is no longer a "person." They will simply cease to exist as a legal entity. They will have no inherent rights, no human rights, no legal standing whatsoever
( op cit )
Which sorta makes it mostly safer, since, well the court ruling DOES include folks who were american citizens before becoming unpersons.

As long as one is NOT designated as an enemy of the state, one can still have all of the constitutional rights that neoCons actually think were granted to them by the founding fathers. The problem of course, is that is conditional on one remaining a human being, who can have legal rights. And gosh, John Yoo's core model was that there is no such idea as 'inherent and inalienable rights' there are only those things which great leader has allowed you out of the wonder of his divine grace.

In related fun we have Guest Post: The Military-Industrial Complex is Ruining the Economy Hum... wow. That not really outsourcing to gain the majik of the privatized economy has not been good at solving the majikal problems of making war a profit center. Hum.... Makes me wonder which side those folks are on, since, well, gosh wasn't rational expectations of the market suppose to provide the divine manifestation that war was gooder! And that the more we sorta privatized it the more it would be the profit center in itself.

Now don't get me wrong here folks, but those of us from the old Red Communist Ike Wing of the GOP, yes, you remember him, the godless liberal heathen who sent in the bayonet weilding bible burning god hating american slaughtering 101st to BUTCHER white christian americans in Arkansas to back the radical left wing Supreme Court, you know them, the one what said that darkies had the same rights as real live white christian males! You know the Radical Extremists Left Wing of the republican party, the party that gets mistakenly confused as the party of the lincoln who opposed slavery and wanted to retain the Union. Well, some of us have been more than a tad bit concerned that the hijacking of the military industrial complex by the same 'fresh water wingnuts' that brought the other recent economic melt downs, and have been championing the sort social conservativism about how the John Yoo krew is right that the president, when he is a white christian male, has all of god's rights to enslave anyone as they are not really people once officially designated as property of the state!

Hum.... Now there is a war winning strategy. We start cutting costs by allowing the US military to go right ahead and designate as property of the state anyone that they want to have as a weapon. This way they could get the kids they want, when they are young enough, so that they are trained right to be the war winning Heroes we all want to see!

Why gosh, teh future is so bright, one has to wear shades!!! We can now have all of the US Government Property we will ever need as a base to secure all of the resources we will ever need, to keep our white christian america, white, christian and American...

Uh, what if this were a good time to get folks back involved in the rational world? Some place where the obvious absurdities were sorta resolved? What if there is going to be a need to overturn the new dred scott case? What if along the way we are going to need to get past the fiscal fiasco of the Military Industrial Infotainment Complex?

What if it were time for a real republican party that was not about the shock jock folly of GlennBeck v. Sarah palin on Fox News Wank Up!

yes, I would probably opt for passing by hash ref, but...

Out there in GOD hating Land, we have
considering revenge on everyone who creates "functions" in perl that pass arguments via hashes. such BRAIN DAMAGE is intolerable.
Which is at times a reasonable attack on the folly of a listIn/listOut system. Especially one that will
allow for 'fat comma', the game of doing
my @gotBack = thisFunction( type => 'a', addr => '', verb => 'add' )
Which is slightly better than the sort of Love that one gets with signatures like
void furBall( string recordType, string ip_addr, string verb)
Where they are all just strings, and of course inevitably some dilbert implements that as
try {
this.furBall('add', 'a', '');
} catch(excpetion e) ...
and then spends some time trying to sort out why they did not get what they expected... Yes kids, that scrawdelous can be done massively elegantly in a variety of badly implemented coding languages.

But then again, as I suggested, I would probably do the fun of passing by reference, hence my code would have been
my @gotBack = thisFunction({ type => 'a', addr => '', verb => 'add' } )
But realistically they should have understood that I probably would have done that in some sort of perlish object, and would of course opted to throw an exception if there was an issue so it would most likely have been say
my @gotBack = eval {
$obj->thisFunction({ type => 'a', addr => '', verb => 'add' } ) };
if ( $EVAL_ERROR ) {
but that way of course leads into the DANGER of actually tossing up, in the carp, die, what ever, an object, vice a mere string, and that way gets into complicated techical stuff. ( did I mention the part about 'use english' - oh well, yes, of course you already knew about that piece of technical knowledge as well... )

Now why is the drieux passing by reference to a hash rather than the fat comma folly? Because by passing by reference I only push one argument onto the stack to call the function, vice the six that would be needed to implement the fat comma solution. All of which reminds us of the most important of all religious commitments:
Every Stack Frame Is Sacred....
So realistically the big up side to passing by hash, ref or fat comma, is that IF the API is really still in flux, which most of them are, till they have some history, the need to ultimately 'improve' by allowing 'but what if we need widgetFlagSnoovelBlark?' then you point out in the next release that in fact one can pass in 'widgetFlagSnoovelBlark => true' and all of the previous code still works, since of course inside of the function, method, what ever, the existence of a widgetFlagSnoovelBlark is left piously in the hands of functionally agnostic, but clearly fullly committed to the TRUE MORAL PIETY, since of course, as we all know:
Every Stack Frame Is Sacred....
And only the demonic coder would ever do anything badder....