Comment Re:there's always Joda Time... (Score 2) 405
Joda actually provides their own TZ update mechanism: http://joda-time.sourceforge.net/tz_update.html
Joda actually provides their own TZ update mechanism: http://joda-time.sourceforge.net/tz_update.html
Joda already provides their own TZ update mechanism: http://joda-time.sourceforge.net/tz_update.html
Also anyone NOT using Joda for dates/times in Java really needs to come to the light and experience the wonders of a well designed API.
Really? Honestly curious what language you're working in. I do a ton of concurrent dev in Java and it is quite easy to write unit tests for. I think almost all of my concurrent code also abstracts most of the problems into a nice class hierarchy that encapsulates most of the threading related code anyways.
I'm not saying there aren't pit-falls but with something like http://www.amazon.com/Java-Concurrency-Practice-Brian-Goetz/dp/0321349601 as a reference it is really not that hard to right solid, unit testable, modular, multi-threaded code in Java. Though it really does help that as of JDK5 there are a lot of really nice concurrent constructs just built into the core API.
Uh, because they know that ads cannot be the income source forever? They need to find the next big thing and be there first or someone else will eventually beat them at their own game and then they'll go poof.
Yet another problem with being driven by quarterly profits instead of long term viability.
Most of the places I've been to in the US use wood frames for houses with maybe a few steel support beams for long open spans
All depends on what you're doing with it. I work on an enterprise level webapp written 100% in java and we have deployments on Windows, Linux, Solaris and OSX-Server using the EXACT same code base and this is an app with over 1000 classes and 250k+ lines of code.
Java has gotos:
loops:
for (int i = 0; i < MAX_I; i++) {
for (int j = 0; j < MAX_J; j++) {
break loops;
}
}
Your premise is equally as bogus. You're assuming that all our enemies could be made to fear us. If your living conditions suck enough it becomes hard to fear anything. What do you have to be afraid of? You likely have nothing of material value and little to no family to be held over you. Death / torture is the only thing they could be afraid of and so what? They are likely in a position where death is always a possibility anyways. How do you make someone with little or nothing to lose fear you?
As for the Michigan Technological University program here is more info: http://youthprograms.mtu.edu/
I went there in early high school for some of the CS camps and came away with a lot of interest and a great head start for college.
I was just going to point about Michigan Tech's Summar Youth Program: http://youthprograms.mtu.edu/
It is a very well run educational summer camp at one of the better small engineering and sciences schools in the country. I did a summer of intro to CS classes while in high school and got a huge jump start for my college career. Also it is a lot of fun and a beautiful place to visit.
Citation?
Many EDUs and other large business campuses use tri-gen plants and from everything I've seen they arguably are significantly more efficient per unit of input engery: http://en.wikipedia.org/wiki/Trigeneration
I think the concern is about being forced to reveal what you've written down while still alive.
My wife and I both have written down our most commonly used passwords including our OSX Keychain passwords. These go into an envelope which has our signatures over the seal and then placed in a lockbox. If someone happened one either/both of us the details on these passwords are in our wills.
I have one of the higher end honeywell models (like $200 for the control panel + remote logic box) that has all sorts of fun options. Maximum adjustment increment, overall max/min settings, etc.
The biggest features I got it for are the external temp sensor which the thermostat uses to adjust the humidifier run time to avoid condensation in the winter and the smart recovery. The thermostat uses a combination of outside + inside temps and some recent historical data (how fast did the house cool down or heat up) to get to a specified temp at the specified time. So if I set it for 55 at night and want it to be 67 at 7am the thing just figures out what time it needs to kick on the heat in the morning so that at 7am the house is at 67. Wonderful feature if you live in the Midwest and you'd have to reprogram a simpler thermostat every month to get the same behavior.
This is as much as I could find about the case: http://dockets.justia.com/docket/massachusetts/madce/1:2011cv11725/139342/
Someone with $4 to spare want to purchase access to the full complaint?
"When it comes to humility, I'm the greatest." -- Bullwinkle Moose