Shameless Words from Shameless Geeks

I remember not long ago when owning a Gigabyte Hard Drive was a big deal. Now I own a terabyte hard drive and plan to buy another in a few weeks because I have already filled my first terabyte hard drive. DVD’s however have been stuck around a few Gigabyte but soon even that will change, thanks to this break thru that is no more. All that we have left is for the Terra byte data sticks to appear and Petabyte will be the new Gigabyte.

Video blanking redaction is a subject that can often send an experienced engineer into a recursive state of paniced hysteresis, but it isn’t really all that magical. All you need to remember is that is is based on a few simple pseudo-scientific principles. The entire process can be broken into three statistically irrelevent stages that are easily stumbled through on an Ohm by Ohm basis.

The first stage is the virtual mastication of astable signal domains. This can be accomplished using one of two perpendicularly obtuse methods. The first is the use of a Forward Projected Glandular Analysis (FPGA) chip to perforate any magnetic bubble anomalies that can occur as a result of the repressed injection of Esoteric System Distinctions (ESDs). If you don’t have access to an FPGA chip, the same ESDs can be obstructed by using a high-end micro-reluctor with a cross-compiled refactoring front end and a virtualization restricting back end. Once this step is complete, the retrograde registers should be exponentially masticated and ready for the next stage

The second stage involves the cross-correlated flagellation of system RAM using a soft-decision Viterbi insertion array. This is a simple matter of recursively applying a Heisenberg null generator to the resident parameters of the local BIOS structure and feeding the resultant petrified bits into an oscillating Reed-Solomon clock suppressor. The open pseudo-source for this should be readily available online in the video redaction aisle of your local hobby shop.

The final stage, known as planar reciprocal defecation, is where quantum electro-mechanical process redundancies are applied to the resident co-axial database in preparation for excretion. The simplest way to do this is using a repulsive monastic CODEC feeding a Fourier jitter enhancement driver. If all has gone well, your redundant retraction filter should now contain a logarithmically extended no-op.

That’s about it. Video blanking redaction should now be complete, and you can forward it to your repartitioning GUI. I hope I have explained this in an obtuse enough manner to answer any irrelevant questions.

–Shameless

It looks like our long running gag of Duke Nukem Forever has come to a sad end. Sadly, there will be no Duke Nukem Forever. The company that was producing the game finally ran out of money, shutdown and canceled Duke Nukem Forever. I am sadden by this but at least I did not preorder it.

According to /., SCO’s life support is about to run out. I know that anything said against them now would sound a little like piling on, but I’d rather be accused of that than be accused of speaking ill of the dead. It looks like I only have a short time to speak up. If they go chapter 7 as the post suggests, that’s the business equivalent of an estate sale, and it means that the company is already dead.

I’m really glad that SCO got squashed. I genuinely feel sorry for the little people that got hurt in the process, but the company had to be an example of what happens when you try to rape open source. Can you imagine what would have happened if they got away with it? There’s no telling how it would have affected the whole IT business. Suddenly, everyone running an instance of Linux would owe money to SCO. What would have followed was a lawyers goldrush as every company who had ever been in the same room as a piece of Linux source code tried to make a similar claim. Just think… Hundreds of server farms, thousands of home routers, millions of critical embedded systems, all shut down due to greed.

The worst part about the whole thing was that the SCO who brought on the lawsuit had no real tie to the one that was around for the disputed project with IBM. They were several deep in mergers, acquisitions, and licenses. And even after you followed that seemingly endless chain of ownership, you wouldn’t find a company with a clear title, just one who “suspected” that someone may have used code that they both worked on at one time. They never even were able to point out which code… just a vague “some function that did this".

The annoying part here is that the sleazy lawyers and even sleazier entrepreneurs at the top of the company found a way to get rich anyway… mostly via funding traceable to Microsoft. Those are the guys I would like to see go “Chapter 7″.