http://en.wikipedia.org/wiki/H...

"So far, no one has been able to provide a compelling answer to why climate change seems to be taking a break. We're facing a puzzle. Recent CO2 emissions have actually risen even more steeply than we feared. As a result, according to most climate models, we should have seen temperatures rise by around 0.25 degrees Celsius (0.45 degrees Fahrenheit) over the past 10 years. That hasn't happened. In fact, the increase over the last 15 years was just 0.06 degrees Celsius (0.11 degrees Fahrenheit) -- a value very close to zero. This is a serious scientific problem that the Intergovernmental Panel on Climate Change (IPCC) will have to confront when it presents its next Assessment Report late next year."

The referenced article this quote was taken from:

http://www.spiegel.de/internat...

Another important topic the climate scientist mentions:

"Temperature increases are also very much dependent on clouds, which can both amplify and mitigate the greenhouse effect. For as long as I've been working in this field, for over 30 years, there has unfortunately been very little progress made in the simulation of clouds."

Keep this in mind the next time you hear, "The science is settled."

Apply it to yourself. You have said nothing beyond what I said, except to claim the contrary.

I'm not. It's a garbage word. There are plenty of garbage words that stick around for no reason other than that people like to use them in place of simpler words.

You used the word. Why did you use it? Because it's simpler and conversational and came naturally to you. People don't generally go around using the word paradigm.

I also used the word "model". Try this: The object-oriented programming model. Gee, does that not get the point across?

And there's nothing vague about simpler words and more common words versus less common words that have come into vogue. Nobody needs a clarification when you use those simpler words. I'm willing to bet at one point you said, "What the fuck's a paradigm?"

I'm not the anon, but yeah, what he said. There are a myriad number of ways to screw up memory in C and C++. But if you want to look like a moron and pretend the vast majority are just null pointers, be my guest.

And yet you instinctively fell into "style" later on, and nothing was lost by using that word. Instead, you gained in clarity of communication. You could also say "model" and it would have the same meaning. "Paradigm" is a fancy buzzword.

Lol, wut? The point of a model is to be predictive, in this case predictive within a range. If the model isn't predictive, it isn't correct. Holy shit. Did you actually learn any science in school?

It's not you being kind, it's you being a dickhead, because I explicitly acknowledged that they were segfaults "in a very trivial sense".

The point being that when a random segfault occurs in a C/C++ program, it could be anything. If you're lucky, the pointer is null. In Java this is a nuisance issue and usually trivial to track down, a typical example being you forgot to check for null when you pulled something out of a collection or similar.

Nice job taking what I said out of context, dickhead. You completely ignored the rest of the explanatory text.

Uh huh, sure you weren't.

If the list goes out of scope and nothing else points to the object in the list, it gets collected. Yes, you can leak memory in Java. No, it doesn't happen nearly as often as it does in a language like C or C++, and you aren't constantly spending time worrying about memory allocation issues to do trivial code. That to me is the biggest thing.

Probably because there's no reason to use such an awkward word in the first place. In this case, notice how you fall into using "style" instead? Also, the vast majority of time, when people use "paradigm", they could replace it with the much more common and simpler word "model" or another simpler term.

An NullPointerException is not a segfault or memory corruption, except in a very trivial sense you can consider it a segfault. The difference is night and day between the kind of memory corruption and wild pointers you get with C/C++.

As for memory leaks, yeah, that can still happen, but it isn't very common and they are easy to track down with VM tooling.

Now if you want to bash Java for not tackling serious issues, just look at its threading model, basically "threads and locks", and it's very easy to have threads stomping on data that it shouldn't. That's corruption.

Java also didn't do a good job for resource leaks, meaning things besides memory, like connection handles.

The evidence is in, and the pause in global warming in outside the range of climate models. But the "science is settled", right?

Oh really? So you think it isn't fair to judge scientists who set out to "hide the decline" in their email (and spare me, I know exactly what was being hidden)? Who ask other scientists to delete email to avoid a freedom of information request on IPCC work?

These emails came out after a leak. I think it is more than fair to judge these scientists on these criteria. That Mann, using work email for a public university, seeks to hide them from scrutiny, isn't inspiring of trust.

Mann's a big fucking hypocrite then: http://climateaudit.org/2015/0...

And the evidence says that the scientists were wrong. Carbon dioxide levels have kept rising, but temperatures have remained flat. The models are out of range.

Try arguing about evidence rather than your feelings.

The long-term trend is a failure. The models were supposed to predict surface temperatures. A recent claim that it went into the deep oceans instead doesn't validate the models. It's over ten years and the models have fallen outside of any predicted range.

Also, the big threat with global warming was supposed to be due to water vapor feedback, as opposed to just the forced warming from carbon dioxide. That has yet to be proven.