September 29th, 2009



The witness testifying in favor of HR 1207 made some very strong points, which was no surprise considering the bill is simply common sense. It was also no surprise that the witness testifying against the bill had no good arguments as to why a full audit should not be conducted promptly. He attempted to make the case that the fed is already sufficiently accountable to Congress and that the current auditing policy is adequate. The fact is that the Fed comes to Congress and talks about only what it wants to talk about, and the GAO audits only what the current laws allow to be audited. The really important things however, are off limits. There are no convincing arguments that it is in the best interests of the American people for anything the Fed does to be off limits.

It has been argued that full disclosure of details of funding facilities like TALF and PDCF that enabled massive bailouts of Wall Street would damage the financial position of those firms and destabilize the economy. In other words, if the American people knew how rotten the books were at those banks and how terribly they messed up, they would never willingly invest in them, and they would fail. Failure is not an option for friends of the Fed. Therefore, the funds must be stolen from the people in the dark of night. This is not how a free country works. This is not how free markets work. That is crony corporatism and instead of being a force for economic stabilization, it totally undermines it.

unloadAndStop()... doesn't.

What types of things will keep the SWF in memory?
This API does not null external references to your SWF, or to elements in the SWF - doing so would be very processor intensive in large projects. As such, any hard references to the SWF or objects within it will prevent collection. For example, if your main application were to reference a movie clip in the loaded SWF such as:

var myFunClip:MovieClip = myLoader.content.funClip;

You can also do this inadvertently with events. unloadAndStop will remove listeners that the loaded SWF created on the stage (for listening to MOUSE_MOVE events, for example), but not in other locations. Something as simple as the following code in your SWFs main timeline can prevent it from unloading, because it will create a hard reference back to it:




I mean hey, it's BIG DEMO, REAL MONEY ON THE LINE, SCREW THIS UP AND YOU PROBABLY WON'T HAVE A JOB TOMORROW time again. So why would I expect Adobe's code to actually work this time? When it never has before?

Yeah, I should expect this bullshit by now...
  • Current Music
    Godsmack - I Fucking Hate You