I can think of a thousand holes in this but it kind of demonstrates how playing ball with someone like the NSA makes all Google's previous "do no evil" actions seem suspect.
Only if Google has played ball with the NSA. AFAICT, there is not evidence of that. It appears that the NSA has spied on Google without Google's knowledge or participation, though.
Because they would fall under FCC Telecomunications Act of 1996, section 702. Which would obliterate their existing business.
Would it? I don't think so. 702 requires telcos to keep their customers' information confidential, but Google does that already. It might be interpreted to require Google customer approval to deliver ads to them; it's not clear how 702(d)(3) would be interpreted in this context. But assuming Google did that, I don't think 702 would interfere with Google's operations (in my non-lawyerly opinion).
The bigger issue is that Google isn't a telephone company.
But if these companies didn't have such huge troves of private user data there would be no need to worry about NSLs, etc. They'd have nothing to give over. He's not against bulk collection of data, etc. He's simply against the government competing against him in the data collection realm.
There's a big difference. The Google data collection is optional for users (Google even provides tools to make opting out easy), and in their individual control. Government data collection is not (unless we collectively take charge of our governments and stop it).
Simply not using Google products won't protect you from this as it is using scripts embedded in web pages. Google analytics Gstatic and Googleadservices just to name a few
Google provides tools to opt out of Analytics and Ads tracking, which will suppress these cookies.
See http://google.com/privacy/tools, the bottom two entries.
The issue is not the average energy price across the country. The problem is local, where natural gas is produced in such abundance but cannot be stored or transported, they practically give it away, which nuclear (nor coal or any other generation method aside from hydro) can compete with.
Oops forgot to clarify, the decays are beta decay, where a neutron in the nucleus turns into a proton and ejects an electron and antineutrino.
U-238 and hit it with a neutron to make Pu-239
IANANuclear Engineer, but isn't it a proton that's needed for that?
After U-238 absorbs a neutron it becomes U-239, which decays (half life = 23 m) to Np-239, which decays (half life = 2 d) again to Pu-239.
Mouse balls are now available as FRU. Therefore, if a mouse fails to operate or should it perform erratically, it may need a ball replacement. Because of the delicate nature of this procedure, replacement of mouse balls should only be attempted by properly trained personnel.
Before proceeding, determine the type of mouse balls by examining the underside of the mouse. Domestic balls will be larger and harder than foreign balls. Ball removal procedures differ depending upon manufacturer of the mouse. Foreign balls can be replaced using the pop-off method. Domestic balls are replaced using the twist-off method. Mouse balls are not usually static sensitive. However, excessive handling can result in sudden discharge. Upon completion of ball replacement, the mouse may be used immediately.
It is recommended that each replacer have a pair of spare balls for maintaining optimum customer satisfaction, and that any customer missing his balls should suspect local personnel of removing these necessary items.
To re-order, specify one of the following:
P/N 33F8462 - Domestic Mouse Balls
P/N 33F8461 - Foreign Mouse Balls
"You stole something and got successfully prosecuted when you were young. Pay me or I'll march around with this sign describing it, in front of your work or any restaurants you go to for business."
Most of my comments are Doxygen, at least from a line count perspective. I try to document every method's inputs, returns and what it reads and modifies and what it is attempting to do.
This part is good. Documenting every identifier is generally not a good idea; instead put the effort into naming identifiers so they're self-documenting. Same with documenting every logical edge; put the effort into making the code itself explain the intent and rationale.
Sure, you have to *maintain* comments along with the code, but the time you save when you have to pick up some code to maintain it later is going to make it worth it in most cases.
Only if you ignore the time it will cost you when the comments are wrong, which tends to be orders of magnitude higher.
So, I don't agree that "comments bad" they are not. In my experience, they are not used enough.
I used to feel the same way, then I acquired more experience, on larger codebases.
For a more complete explanation of why comments are bad, I recommend Martin Fowler's book "Refactoring: Improving the Design of Existing Code". There are a few other books that cover it as well, but I think Martin's chapter on the topic explains it concisely and effectively.