Comment Re:"Could", (Score 1) 401
Nah, if he was so confident in that prediction, why did he later change it?
Wow! You've even opted to ignore most of the more optimistic projections!
Which ones are you talking about specifically?
There is quite a bit of work being done to understand where all of the heat is going, but that has been discussed on here before.
That's one way to describe it, and certainly some scientists are inventing some complex hypotheses for that purpose.
A more simple scenario is that the earth isn't heating as much as expected (which mainly means that the feedbacks aren't as significant as some scientists hoped).
What's the real mission here?
Given that his congressional district would benefit a lot from money spent on space exploration, I'm guessing his goal is to get money to his district.
We are very close. Our society overproduces enough now (and throws out about half!)
Close? Yeah, all we have to do is invent AI, right?
This is subjective. But it certainly goes beyond "remembering whether to capitalize the first character of your methods and variables", at least if we're talking about idiomatic C# vs Java.
That's true, sometimes I forget and accidentally type 'foreach' instead of 'for.'
Seriously though, the differences between Java and C# are miniscule compared to the differences in other languages. I spent the evening reading A Method of Programming. No one will ever look at that and confuse it with either language.
There is one good reason for avoiding checked exceptions though. Interfaces. In Java it is required that either 1. all exceptions that might ever be thrown by implementations of an interface be declared at the interface decleration or 2. all exceptions be bundled in RuntimeExceptions to short circuit the checked exception mechanism anyway (with the potential side effect of ruining stack traces).
Just throw Exception, unless you have some specific behavior change that can happen if a different exception is thrown, in which case you can throw Exception AND the SocketException (to use your example). Problem solved. RuntimeExceptions won't be bundled with that.
As far as catching exceptions go, imo unless you are going to do something specific to deal with an exception, then catching it is bad coding practice.
That depends on the error handling strategy of your program. It is especially important if you need to release resources. Either way, it's good to let the callers know what to expect.
There are enough differences to matter.
Not really.
Their goal will always be to lock you into their vertical to protect their verticals.
That's a good point.
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?
