The longer I think about it, the likelier I find it that time is in fact an emerging statistical behaviour equal to the entropy arrow of time. That would allow for local statistical reversal of time, and balances out any difficulties of cause and effect, where the difference between cause and effect is defined as effect having a higher entropy than cause. I have a nagging feeling a lot of things may be involved in this (even P ?= NP can maybe seen as a form of this, where an unsolved problem describes a system with the same energy as a solved problem, but the unsolved problem has higher entropy). Unfortunately, I lack the rigor to properly work something out. Feel free to downvote based on crackpottery.

Java on the browser very much corresponds to the cliche of the horribly misshapen monster moaning "please... kill me". Java - or at least the JVM - outside the browser seems to be doing fine. Scala, Clojure and Groovy are thriving, and starting to get mature, Kotlin is hot. Java frameworks are doing really well in webframework performance. The JVM might be in better shape than ever at the moment.

That's assuming that java will not have two critical patch updates on the same day. On the one hand, that sounds reasonable. On the other...

Don't fix it. Once it starts causing problems and you see no upside in maintaining, remove it. Easy as that.

Of course, if you'd referenced the citation directly instead of referencing Wikipedia which references the citation, it would have been clear from the outset where the information came from

It isn't, and that kind of behavior should be punishable, I don't think many people disagree with that. Saying something like "Did you think there was a bomb in there or something" to the TSA is not actually the equivalent of yelling "bomb" though.

Don't you recognise that it is a problem you can't make these kind of jokes at an airport or at the TSA? Yes, it's probably a bad idea to do this. But it is ridiculous that it is a bad idea.

Oh, it must be true then.

5oz of liquid is ok. But only in a terrorist-proof plastic bag. 2 gallons of liquid is also OK. But only if you drink it. I don't know much about toxicity and explosives, but I'm pretty sure there must be at least some liquid explosives that will not kill you until airborne.

It's not that they have any obligation to continue anything, it is just that people start to avoid google products they may become dependent on, because their services have a good chance of disappearing. I use Google Reader a lot. It sucks that it's going to disappear. Google is in their full right to make it disappear, but it sucks. Now google is introducing Keep. I'm not going to use it, because it might disappear on me, when I have become (sort of) reliant on it. With this policy, google is hurting itself, because people become weary of adopting google products in their daily routine.

Isn't that what being a programmer is all about?

Typing in all caps is considered shouting, please refrain from it. Also, ROT13 is traditionally capitalised.

And counting. Wake me up when http://bugs.debian.org/release-critical/ hits under 20.

Actually, I prefer the logic separation between a subroutine (that modifies state, and doesn't return a value) and a method call, that shouldn't modify state and does return a value. Obviously, many method calls do modify state, and sometimes that is even useful, but being able to declare the difference is a win IMO