I had a cheap combined machine and it was absolute shit and broke down after a short time. Not advisable. Generally, separate machines work better.
Slashdot videos: Now with more Slashdot!
And unlike vacuuming, i can switch on the laundry and go do something else.
I have a Roomba
That isn't common in my area (western part of Germany). You typically have your own washer / dryer although there might be a specific room in the basement where everyone puts theirs. Many people have them in their kitchen or bathroom, though.
So you're not making green tea, then?
I find running Java inside a browser to be, to put it politely, fucking retarded.
You're talking about applets, he's talking about having an application server serve HTML. I suppose.
OSX comes (used to come?) with outdated versions where a lot of Java programs don't run properly
Who cares what version is installed by default? OSX can be upgraded to the latest version, and any application that needs it ought to provide an installation package that does precisely that, or at least clear instructions to the user on how to do it.
As the person responsible for packing our commercial desktop Java app and maintaining its installer, I suggest just bundling the JVM with your product, but not as its own Installed package but inside your installation. It takes a bit of additional hard drive space if every app has its own JVM but it saves so much confusion and different version failures. The end user also doesn't have to worry about the abysmal Oracle updater because our JVM is not registered to handle browser applets or other stuff, so that security risk is just not there.
Wouldn't a Raspberry PI be enough to emulate it at perfect speed?
I like discreet GPUs...
Maven is great when you are ready to give up many freedoms in how to setup your build structure and do things exactly as intended. Then it works very well. Most of my projects work with a single parent pom defining stuff like metadata, repositories, java version, a project pom for every module with nothing more then dependencies and a single aggregator pom bringing it all together. if you stay simple, Maven is great. If you want to do complicated stuff, stay away from it.
In my personal opinion, that is a great way to do things. Leave the individuality and innovation to the software, let the build system be conservative and dumb. A well written Maven build is short, uses few plugins and is easy to read and understand. It still needs work to set it up, learn about the right way to do things and possibly change old habits.
I you are not prepared to give up individuality in your build system, stay away from Maven, there are better tools for scripting a build.
Very delicate! Mmmmmmh... Sauerbraten!
Well, germany rears about 30 million turkeys a year.
You have been referring to "importing energy" before, but now you're talking about electricity. Germany exported more electricity in 2012 than they imported. And I have a source for that:
Where is your source?
Germany imports most of its energy.
Technically you're right, because we import lots of oil, gas, natural gas from countries like russia. But I wanted to add that we actually export more electric power than we import. Of course, part of that is produced with the imported resources.
I guess Java installed via java.com or such packages on PCs is going away. Most of the stuff in Java runs on a server anyway. Applets/JavaFX were never that useful. We still develop a desktop application in Java but are seriously considering just bundling a JVM with the app and be done with it. Btw. that's the only way to get a java app into the Mac App Store - Not that I have ever tried to do that.
The only thing I will miss is Webstart - I really liked the concept.
Availability can be a bitch... Shows can disappear from a streaming service, probably because of licensing.