HN user
I'm as strong a supporter of a citizen's right to encryption as anyone, but I actually think that Mr. Comey's testimony was accurate and forthright, and his framing of the issue of encryption as it relates to the capabilities of law enforcement was appropriate and well-reasoned.
From the section you referenced:
"He [the President] shall have Power, by and with the Advice and Consent of the Senate, to make Treaties, provided two thirds of the Senators present concur;"
I think that your claim that the only role of the Senate is that it "must be notified in the event the President has made a sole-executive agreement" is a misrepresentation. In fact, the Senate must vote to approve every potential treaty before it becomes valid.
I disagree very strongly with your purported equivalence between Karunamon's argument and that of the NSA.
My primary problem with the NSA is that they (a) use their position of power to install backdoors in hardware/software/infrastructure, (b) do it in secret, (c) claim to be in some way "above the law" w.r.t. secret courts, (d) use public taxpayer money, and (e) motivate their behaviour using bogus anti-terror claims. None of these infractions exist in the "right to be forgotten" scenario.
Fundamentally, in the story of the NSA, it is the NSA that is in a position of power that can and will be abused. In this case, it is the power to scrub the entire internet of information by imposing centralized censorship which, in my mind, is simply too much power to put in one place.
Did you try it? It gets the 4+6+5 and CVC on the front just right!
This is a ridiculous stance, in my opinion.
Part of the appeal of libraries is abstracting away implementation details. I want to be able to have foo.h #include a hash table, or a binary search tree, depending on #ifdef's or its internal implementation. The user of foo.h shouldn't even have to know about it.
I agree with your premise (re: abstraction of implementation details), but I think you've applied it incorrectly to reach the wrong conclusion.
If the implementation of foo (contained in foo.c) uses a hash table or binary search tree, then foo.c may of course include whatever it likes. On the other hand, foo.h is (by definition) the interface to foo; any headers the interface requires (e.g. for function argument types) ought to be explicitly understood by the user of the library.
"The real WTF (that you, me, and the OP probably agree on) is the California initiative process, which forces/allows citizens to act as legislators."
I definitely agree with this (-:
You're right, in that a reasonably informed voter should have known the nature of the proposition. Unfortunately, due to the broken initiative process, those weighing the options tend not to be sufficiently informed. In my opinion (though not that of the US Supreme Court, see Calder v Bull), such ex-post-facto tax laws should be as prohibited as similar laws are in criminal circumstances.
While your points may be entirely true, in my opinion they are no excuse for failing to make clear the retroactivity of the proposition.
Just a correction: the code is actually perfectly portable. The integer constant 0 is the canonical definition of the null pointer by definition in the standard (See Section 6.2.2.3 "Pointers" in C89). The null pointer constant (NULL) is defined primarily for convenience (so a reader knows you mean a null pointer instead of a arithmetic zero). Of course, the bitwise representation of the null pointer need not be all-bits-zero; that is, NULL = (void )0 != ((int *)&0).
Just a note - all radiation levels reported from around the plant are measured in milli(m)/micro(u)-sieverts(Sv) per hour. For comparison, the worldwide average background radiation level is approx. 0.274 uSv/h, and the usa recommended continuous occupational limit is 5.71 uSv/h. For example, the highest level I've seen reported is 400 mSv/h, or 70000x the recommended limit. Info from wikipedia.
Of course this isn't a feature of the language -- but most implementations (e.g. gcc) technically allow this, if you really, really know what you're doing. For example:
http://www.cesarbs.org/blog/2010/07/19/run-time-machine-code...