justincredible

While partitioning these cultural attitudes and artifacts by decades is a useful heuristic, I often feel like the actual cutoff point is around mid-decade. The late '80s feels closer the the early '90s than it does the early '80s.

Would it take too long or is it just that the margin is too small?

The article isn't very clear but assuming it's a 16-bit numerator and 8-bit denominator, then MSN's answer to [0] lays it out (although for higher bit sizes). If the denominator was 16-bit, then the top-rated answer (by caf) to the same SO question seems like another approach, but that wouldn't be a one line change.

[0] https://stackoverflow.com/questions/2566010/fastest-way-to-c...

Huh? He's saying that caloric restriction does work, but many people only achieve that by temporarily restricting their food options.

The idea that dieting is a temporary change to your food habits is why most "diets" eventually fail.

My layman understanding would be that you're not gaining anything other than a more abstract model. If you want performance, the code is going to boil down to the equivalent linear algebra + quaternion operations.

Another situation where the intuition breaks is that a repo can have branches without a common base (i.e., disconnected graph).

Definitely unusual, but sometimes I want to move a folder between repos while preserving the commit history of the folder[0].

[0] https://stackoverflow.com/questions/41811986/git-move-direct...

I've usually heard this phrased as the signature implies only one possibly function, but that is in a very abstract sense. This phrasing is more intuitive as it's saying the signature constrains what the function could possibly do.

For example, if you have a function of type ℕ x ℕ -> ℕ you know it could be doing addition, multiplication or exponentiation, but it can't do division because then it could only be a partial function. A more abstract signature ℕ x ℕ x Op -> ℕ, where Op is the set of binary operations on the natural numbers, can really only do one thing (apply the operands to the operation).

Another example, [A] -> A could be any fixed indexing function, but it can't be a function that produces a value of A not found in the list as the true signature of that function is just A per se.

As a sibling comment points out, in the context of programming the signature isn't as constraining as it would be in maths as the distinction between total and partial functions is often ignored and you can have side effects. But the more you model your functions to be pure and total the more you can reason about them abstractly.

I agree that they shouldn't have re-edited the movie based on Carrie Fisher's death IRL, but that scene is a masterclass in bad writing.

Rian's intention was to demonstrate some semblance of humanity remained within Kylo. But the optics are that he is truly weak and in the end isn't even bothered much by the (for all he knows at the moment) imminent death of his mother. Had Kylo fired the shot he at least would have surpassed Vader in evilness, whether or not Leia saved herself.

I agree with the "fans" that she should have died in that scene, but since Rian was too scared to snuff Leia before Luke the scene shouldn't have been written in the first place.

TIL .pl is for Poland. The misuse of .io is probably more common.

Rust compilation is strict but not cruel. The suggested fixes associated with compilation errors are very friendly to beginners (one notable exception is errors around lifetimes).

Your concerns regarding "feature creep" are reasonable and would be expected for a language trying to displace C++.

Edit: grammar

[flagged]

It solves the problem of the child getting the wrong answer until they have to read a real mechanical clock.

The orbit is closer and farther at different times of the year, but that is not the reason for the change of seasons.

Even numbers end with even digit

True (in even bases).

Since 30 is even so must be 0

This is essentially the converse of the previously statement. Fortunately, the statement is based off an equivalence so it is also True.

Idempotent means feeding the output back in as the input will result in the same output. It might require purity, but is conceptually distinct.

For example, boolean negation is a pure function as it depends only its input and has no side-effects, but it's not idempotent since: not(not(var)) != not(var)

The confusion might be due to everyone using concurrency to mean concurrency and/or parallelism.

I believe it was God who included it, Moses just wrote it down.

The request is unreasonable, but is the second question not valid?

To be precise, the "bomb" was being obfuscated by the password, not the password per se.

Most of the answers to that last question are inane and unproductive. The first answer is funny though: https://www.quora.com/What-is-1+1

Didn't the investigation end when the report was released?

Did you mean < 5 years?

You can disable all location services. The incorrect impression is that a user has complete granular control over the use of location services.

Secure but inconvenient has an immediate and visible downside, whereas insecure convenience has delayed and nebulous downsides. Convenience will always win when appealing to the lowest common denominator, but maybe we can have both.