4 thoughts on “Five Years Later”

  1. That speech was from when they were running Obama 1.0. Back then he had enough free resources to run a fully real time text-to-speech synthesis engine. But when additional processes started be executed like ‘HeadOfState.exe’ and ‘NetSpedingCut.dll’ the kernel crashed and it got stuck in an infinite loopback of stuttering and strawmen. Most likely because the ‘Community Organizer’ service that’s constantly running in the background seems to consume far more resources than what it should really call for. So, at some point a few years back it looks like they tried to wipe and reload the O/S with Obama 2.0 in an attempt to optimize the Executive branch instruction set. But so far it has only been able to handle a series of lightweight apps that give the impression that it’s actually doing something novel with its slick UI. However, it quickly gets bogged on anything but the most trivial of tasks. Sometimes even going so far as to just unexpectedly shut down and go into a Hawaiian vacation safe mode. Sure out of the box it came preloaded with a bunch of shortcuts to some free apps like, “Campaign Cash Finder Pro”, “AttacK Watch Anti-Conservative Endpoint Protection”, and ‘Tiger Woods PGA Tour Online’ but damn if there doesn’t seem to be an obvious way on how to uninstall any of that. And trying to install your own apps is a futile exercise without first paying the $40,000 to access the platinum level lobbyist support services. Although it does appear some Wallstreet insiders have managed to find a back door and setup their own daemons in a protected memory space. But you have to have some seriously expensive hardware to be able to pull that off and that’s something just not anybody can come with. I say we just sell this model to a university or a political action committee that might find it marginally useful to just reload Obama 1.0 and set it up to run teleprompter bobble-head subroutines all day.

  2. Most likely because the ‘Community Organizer’ service that’s constantly running in the background seems to consume far more resources than what it should really call for.

    That’s usually caused by a memory leak.

  3. They tried to patch that with Wright_Ayers-wrapup(2008.001).exe but there was a fundamental illogic in the error control trapping code that necessitated a full up versioning.

  4. There’s a memory leak? Then let’s buy more memory so he never runs out. It amazes me how people who have no business being around a computer thingie can pussy foot around when the answer is so obvious!

Comments are closed.