> ...to advance religious doctrine, which is the only reason these issues are ever raised in the first place...

Because that's exactly what third graders are doing when they ask questions in the classroom. Advancing their religious doctrine. Down with inquisitive third-graders!

Seriously. Slow-change Darwinism? Ya that explains it all...

Oh man, you must get positively turgid when you read new licensing models and agreements for crap-products that don't even exist. I mean. What a wonderful world where it's impossible to actually *buy* anything and all anyone can ever do is "license".

Don't mind the guys writing stuff that's useful and works and then giving it away for free. You'll find a way to litigate them out of existence, or criminalize them (DMCA).

> First year law school stuff.

Ya, the "wet dream" part...

Ever hear of Common Law?

http://en.wikipedia.org/wiki/C...

Note: Judges are lawyers too.

I think the point is: If you didn't *get something* out of the contract for what you're *putting in*... It's very often not a valid contract.

foo: "Sign this document that I get all your money."
bar: "Okay."
*bar signs*
foo: "Muwahahah, I'm so smart!"
*not a valid contract, foo is gonna get reamed in court*

foo has to at least *pretend* (like a cell phone carrier) to have given something valuable to bar in return for the money...

JOIN vs sub-query? I don't know what DB or problem sets you are working with, but if it were MySQL, for instance, MyISAM just seems to run many sub-queries much faster than similar JOIN logic.

In any case, reducing working sets (when there's not a simple index mapping) can be very important for getting any kind of performance. sub-query shines for that, (perhaps in a JOIN at times) JOIN by itself doesn't.

Expecting a certain slant on which is better (JOIN vs sub-query) just smacks of personal bias. (unless perhaps they've re-written the same sub-logic 10 times and aren't receiving serious performance gain)

According to the article "unstable code" is anything with undefined behavior according to the C++ standard. This could be as simple as an integer overflow or divide by zero which in debug or "zero optimization" mode would always cause an error, but which in an optimized release may simply be removed.

I think momentum is an important term to remember here. Photons may not have rest mass, but they do have momentum. (in classical physics: p = m * v)

I just have to point out a bit of a seeming discrepancy here. From the wiki article on ERP:

> However, information tools like ERP are expensive, and not a practical method for medium or small business owners.

Actually, if you've got tick-marks at the integer level, then you should be taking measurements at 10-times that precision. ie: deciding between 1.4, 1.5, and 1.6 for that "half-way" dial by looking at how far the dial is above the top of the previous tick-mark. The scale doesn't precisely measure beyond that resolution. Didn't any of your labs teach this?

Accuracy is a whole other subject usually involving comparison of a measurement with something "real" (often through other measurements).

If that software is GPL code you stole from the author, then YES!

If alternative free software is readily available and you're blocking it in an attempt to shovel your crap-ware, then YES!

And yes, I'm a programmer and I live with a strong sense of entitlement when it comes to controlling what software I put on my systems. I'm entitled to be EXTREMELY selective about any bit-stream I might decide to run, especially those that cost me cold hard cash.

You're kidding me right? Tons of really talented people have spent large portions of their life creating software that they'd merely love for me to be able to freely use and I'm in entitlement mode if I want to honor their work by using it as originally intended?

Lynx anyone? Also, you don't have to leave the command line to use it.

I'm confused, are you saying the whole token system is poorly designed? The database should only contain the public key equivalents for the physical token generators. The private key equivalent data shouldn't exist anywhere outside the key-fob.

(It's like you're saying stealing the password file would give you remote access to a UNIX system, without further decryption/password guessing)