I immediately found a very large irritant after upgrading. Previously, I had line-in set to play through to the speakers. There was a simple slider in sound preferences that existed back since at least 6.06. The same option exists under Windows. But suddenly, 9.10 removed this option. Line-in no longer plays through, and the option has been completely removed from the revamped (and somewhat disorganized) sound preference panels. I appreciate the effort to "modernize" the sound options like per-application tuning, but not at the cost of tossing simple, basic options that have existed since the invention of the sound card.

Also, regarding the bootup animations, they've changed for three or four consecutive upgrades now. I don't mind a refresher when appropriate, but "refreshing" every six months tells me that some priorities need some reordering.

So you say that the work required moving the cold water to the hot water is necessarily equivalent to that of directly heating the water. What if the water is 1mm away? 10m away? 1000 light years away? The work required for each of these is equivalent? Did you just discover a way to move water 1000 light years minus 1mm for free?

The problem with your "basic physics" is that work is equivalent only when the outcomes are exactly the same. Think about why heating x liters of water is not the same outcome as raising x liters of water some height.

Let me offer another example. Suppose that we want to heat 1L of 1-degree-C water to 50 degrees. It just so happens that we could move the 1L of water .00001m into thermal contact with a close-by 1L of water kept at 99 degrees. Now, the outcome of heating 1L of water to 50 degrees is the same, but the outcomes of the universe outside of that narrow scope are not identical. Opting for a 40% (or even far, far less) efficient mechanical pump saves energy over a heat pump heating the water 49 degrees because the work required for the two processes is not equivalent. (And, of course, if .00001m is changed to some obscenely large distance, opting for the the heat pump instead would be more efficient.)

A tip for both you and the submitter: fiance is the groom, fiancee is the bride.

There's also an accent on the first e, but I'm not going to attempt it because Slashdot eats my unicode for breakfast.

No, it's not incorrect, you just failed to understand my point. You are isolating this study from other research and taking it at face value, whereas I am putting it in the context of substantial previous work and knowledge.

Imagine there were a study that correlated people letting go of things and those things falling to the ground. Taken at face value, as you do with this story, one should ask, for example, whether something else caused both the letting-go and the dropping-to-the-ground. But taken with previous knowledge, that would be an exercise in pointlessness; we all know what gravity is and that it exists, and so we can conclude that letting go of things is in a causal relationship with those things falling to the ground.

In other words, pedantry doesn't do anyone any good here, because we already have substantial evidence applicable to this new work. I appreciate your and the community's attention to correctness, but in this instance, it's being misapplied.

People, please stop tagging every study on Slashdot with correlationisnotcausation. I know it's standard here to believe this community is somehow more enlightened than all others, but do you really think that researchers became researchers without being able to ask simple questions? In fact, in an idealized study, it's not even a relevant question!

Moreover, this moronic practice is especially stupid for this story because the neurological effects of lithium salts have been explored for decades. This is not a revolutionary study by any means. So unless years and years of studies have gone horribly wrong, then yes, in this case, correlation does, in fact, imply causation.

If you voluntarily incapacitate yourself by getting drunk, you're responsible for any and all contracts you enter into while impaired. See Lucy v. Zehmer, the "heh, sure, I'll sell you my house for $100. I'll even sign a contract. I know you don't have a hundred dollars on you- oh, crap" case.

Erm ... that's not even close to what Lucy was about. Lucy had little to do with intoxication. Straight from the op. Ct., "In was in fact conceded by defendants' counsel in oral argument that under the evidence Zehmer was not too drunk to make a valid contract."

Lucy revolved around whether the contract was valid based on "outward expression" rather than secret intent. Zehmer claimed he was "joking", despite talking for months about it, despite writing it down, despite getting his wife to co-sign it. The Court found that Lucy entered into the contract in good faith. If this contract weren't valid, how could any reasonable person want to enter into a contract ever without mind-reading capabilities?

Not only did Lucy actually believe, but the evidence shows he was warranted in believing, that the contract represented a serious business transaction and a good faith sale and purchase of the farm.

..."We must look to the outward expression of a person as manifesting his intention rather than to his secret and unexpressed intention...."

And that's why Lucy is taught in every contract law intro class.

I don't think you're quite as clever as you think you are.

So if you are not held back by external requirements like dependencies on packages or third party software that hasn't been ported to 3.0 yet or working in an environment where everyone else is using another version. If you're learning Python for the first time, 3.0 is a great way to learn the language. There's a couple of things that trip over beginners have been removed.

Like basic grammatical structure, for instance? When did Palin become a Python dev?