Note that the IRS does pay (pretty good) interest, if they owe you enough.

I found that out one year when cleaning up the mess resulting from a forced stock sale (due to a takeover) and a broker that did backup withholding for the entire amount, ignoring the cost basis; but reported to me that a smaller number of shares had been sold, and that nothing had been deducted. After a few go-rounds I got the corrected paperwork in June, and filed a 1040X.

The extra check for the interest was a nice surprise.

Not really; payments appear to have been broken since dice took over.

The grounding is a trick; it just ties you into the Earth's energy fields, and makes the mind control easier.

Just remember:
* Shiny side out blocks mind control.
* Shiny side in blocks reading your thoughts.

You have to pick one!

Ever look at the contents of /System/Library/Extensions/Dont\ Steal\ Mac\ OS\ X.kext/ ?

I picked up a 360 with Kinect for my parents a couple of weeks ago. Controllers are becoming more difficult for them to use; and I figured controlling a game with whole body movements would work better for them.

So far they've really enjoyed it; it seems to be a good fit for the same casual gamers who have been using a Wii, but want games that are a bit more complex.

The problems which are solved are used to generate checkpoints in a distributed proof-of-time system which is then used to impose a partial ordering over a list of transactions.

They've been there for years; haven't you noticed how some drivers mention the organization that sponsored writing them?

ELKS is a subset of the Linux kernel that can run on 286 chips.
http://elks.sourceforge.net/

On rural roads it can be handy when your GPS alerts you that 110 miles ahead there was an accident, and the road is now closed. In 50 miles, you should turn left, then right in another 30, and approach your destination from the other side so you don't have to backtrack when you reach the closure.

It can also be handy with mountain passes that close suddenly after rockslides. Often while there is an online notification sent out, they only post signs a mile or so away from the closure, and not 40 miles back where the last branching road was.

At the local mall, there was a "Babbage's" and an "Electronics Boutique" right by each other. They would always try to undercut each other, so you would want to check both.

I remember one stuck with the old 8 bit systems for longer than the other, but I can't remember which.

There was also an odd local store which stocked Atari 8 bit series stuff until at least 1995; they had only Atari hardware; ST and Falcon 030 computers; and Jaguar game consoles.

This is why most projects require signed statements from new contributors stating that they either own the code they are contributing, or have permission from the code owner to contribute it.

If someone lied, and submitted code owned by an employer without the employer's permission, it can be a real mess to resolve.

If you don't actually own the rights to what you are writing, please don't contaminate open source projects by including code owned by your employer.

Cleaning up a contaminated code base is a big pain. Please make sure you own the code, or have the rights to release it before setting it free.

You should have negotiated this before you started employment.

Once, when I objected to terms that would have granted the company ownership over everything I did outside of work, they just swapped out that page with another one they had ready. The different terms were there and ready, but just not the default. They were perfectly happy to give me the rights to my own projects, as long as I was willing to ask for them.

It does suck when you didn't pay attention to what you signed, and are stuck in a bad situation, and it can be hard to fix these things after the fact.

Your best option would probably to look for another job, and pay attention to what they are asking you to sign.

Hopefully you don't have any long term non-competes, or other clauses.

My guess would be memory fragmentation; Firefox requests and releases pools of memory from the OS rather than making OS level requests every time it needs memory, and unless a pool is completely unused, it can't be released.

So there is some additional overhead of space that is free for use by new internal requests, but can not be released back to the OS.

The general opinion is that the LGPL bars distribution of a statically linked binary containing non-GPL family code combined with LGPL code.

You might be able to get away with providing object code for both your binary and the library, but that makes RMS sad.