cobbal

RGB isn't white, it just looks that way to us. True white has every frequency in it.

Color is an infinite-dimensional space since you can have any amount of any frequency EM waves. Humans eyes reduce that infinite dimensional space to 3 dimensions, centered on RGB.

Interesting.

I still think it would be hard to apply to a ref counter app, since you'd need to keep track of change in ref count for later cleanup (thread-local per object maybe? sounds inefficient), but I now will admit that it sounds possible.

Possibly, but it's very handy to let immutable data be read by any thread that wants to. If, however, it's very slightly mutable due to a ref counter, you have to atomically manage the counter, even for what should be free immutable reference.

It's probably not that much, on a global scale. What's more, CO2 is a better gas to be venting to the atmosphere than methane is. [citation needed]

I usually try to stick it all on one line when I have to do that, something like

    ssh somehost 'cd /some/dir; grep -lr foo .' | pbcopy

not very flexible, but it works for many cases

With the right zsh plugin, either of them will tab complete properly. (I think "osx" from oh-my-zsh is the one that does it on mine)

Edit: looks like this is actually built into zsh. Slightly surprised, but just goes to show I know almost nothing about the shell I use every day.

Linear in this case means y = m * x. The relationship between Fahrenheit and Celsius is affine (y = m * x + b)

For gory details: https://en.wikipedia.org/wiki/Affine_transformation

From the article:

> In my experience, the spiped tunnel is highly reliable and recovers more gracefully than a standard SSH tunnel.

I've never had an issue with ssh -D though

Still, when lightsabers clash you never see them bending as the article claims they would.

Well, yes and no. If you're just talking about integer primes then sure. If you consider gaussian integers though (a + b*i where a and b are integers) then you would have to say "the gaussian prime numbers that aren't 1, -1, i, or -i.

The definition of primes that excludes units makes sense in more places than one that includes units (especially once you start talking about prime ideals instead of prime numbers)

It would be harder, but the developer console has access to closures as well:

http://stackoverflow.com/a/16048707/73681

Another fun thing to do with that phrase is consider its contrapositive:

That which doesn't make you stronger, kills you.

Which is equivalent, but more obviously absurd.

Yeah, but it's not always easy to see every possible security issue. For instance, your proposed solution of just rounding the distance to the tenth of a mile is scarcely better. The attacker will just need more than 3 points to be able to locate with as much accuracy as they want.

At least I hope that's not how this issue was fixed; article doesn't say.

Which was in no way influenced by c++

Yes, but I suspect the NSA has had the foresight to backdoor most major brands of lava lamp. Same problem as before, you can't easily verify the hardware.

Actually, I've used Stack Overflow to learn things by trying answering questions I don't know much about. Most of the time I don't succeed in answering them, but I always find out a lot while trying to research/figure it out.

Your mileage may vary

personally I use HEAD quite often in the form of `curl -I` if I want to check the size or mime type of a particular resource.

I'm not sure, could get confused with the web template framework in WebKit.

https://github.com/WebKit/webkit/tree/master/Source/WTF/wtf

My take on this has always been the pointerness is semantically part of the type, but syntactically it belongs with the variable.

Therefore I annoy both parties by putting a space on either side to protest the fact that everyone is wrong.

The beginning of the proof starts with "Suppose to obtain a contradiction, that mathematics is inconsistent".

From that assumption, they derived a contradiction, therefore the assumption can't be true, and math must be consistent.

It probably refers to the fact that variables by default are global. If you prefix them with var they're function scoped, but there's no way to make them local to the curly braces of an "if" statement.

In scheme, lexical scoping is easily accomplished through the let form, and it's pretty hard to make a variable global by mistake.

So yes it does have lexical scoping in the sense that function arguments are lexically scoped, but that's the only scoping environment, and you can't hide that fact behind macros like you could in scheme if it was needed.

Yes and no. You could argue that use of passwords or private keys is security through obscurity, but that definition is pretty meaningless. Security through obscurity doesn't really apply when you can make the search space arbitrarily (often exponentially) big very cheaply, as is the case of URLs here.

True, but purely mathematically every cipher is vulnerable to the "get lucky and guess the key right the first time" attack (OTP excepted of course).

Almost all crypto operates in the realm of absurdly close to certain.

I think the criticism of the loop is a bit unfair. If your random number generator returns >250 a thousand times in a row, you have bigger problems than slowness.

Actually, make works in tramp by default if you use 'M-x compile' and friends.

Pure speculation, but I would assume Apple will be a "whitelisted developer".

related: you can set it to be silent by default in System Preferences; then shift will make it not silent.

10.7.4 is when it was reintroduced I believe:

http://apple.stackexchange.com/a/53073/8035

Unfortunately, what Amazon has to secure is almost every account. 2 factor authentication is great for the more security-conscious, but that's a very small percentage of Amazon's customers. All the scammers would have to do is hit one of the 98% of accounts that just have default security.

Sure, it can protect your account, but it can't protect Amazon unless they force everyone to use it (which would obviously not be good for building customer loyalty.)

What's worse about the __sub__ method is that it will work in unpredictable ways, for instance

  >>> ExpressiveList(item, [2], [3]) - item

will either be [[2], [3]] if item isn't a list, or something different if item is a list. This goes against the "Explicit is better than implicit" philosophy of python, and can cause all sorts of headaches later.