Love and Hate For Java 8
snydeq writes "Java 8 brings exciting developments, but as with any new technology, you can count on the good, the bad, and the headaches, writes Andrew C. Oliver. 'Java 8 is trying to "innovate," according to the Microsoft meaning of the word. This means stealing a lot of things that have typically been handled by other frameworks and languages, then incorporating them into the language or runtime (aka standardization). Ahead of the next release, the Java community is talking about Project Lambda, streams, functional interfaces, and all sorts of other goodies. So let's dive into what's great — and what we can hate.'"
So you're saying that *all* programming languages are exactly as good each other then? Perhaps you are spending too much time in the "real" world?
Sure: reimplement it in Java. Even better, use it within J2EE so that it takes 45 seconds to start up.
May you spend 100 years in purgatory, writing AI programs in COBOL.
Lisp may be an interesting language, but Lispers scare me. The glow in their eyes when they evangelize about the Mother of All Languages reminds me of Village of the Damned.
Sure: reimplement it in Java.
That's called Clojure.
Even better, use it within J2EE so that it takes 45 seconds to start up.
They sped it up?
They're still waiting for the application with the answers to start up.
Mod me down, my New Earth Global Warmingist friends!
Java 8 is still limited to 32-bit array indexes, meaning, e.g. that arrays of doubles are limited to 32GB. Java won't get true 64-bit support until Java 9 in 2016.
32GB should be enough for anybody.
"Knock Knock..."
"Who's there?"
...
...
...
...
Java!!!
Someone flopped a steamer in the gene pool.
Why would you need an array longer than 2^32? Unless...wait, are you sequencing alien DNA????
I swear to God...I swear to God! That is NOT how you treat your human!
I used to work on a Java transaction processing application at a major financial institution that handled more than 1,000,000 transactions a day that consolidated data from Unix, mainframe and Windows systems. The transactions came from batch and online, client-facing applications that had five nines uptime requirements.
I don't know, sounds major to me.
That looks like only 12 transactions per second to me. But then, I guess that's about all Java can handle between garbage collections.
More seriously, we use Java for various server systems with high uptime requirements, but there's usually C++ stuffed in there to handle the performance-critical parts.
Well, you have to instantiate a BigDecimaFactory in the inversion-of-control container and pull in a lot of org.apache.whizbang.dont.we.love.us.some.nested.hierarchies code, plus update your ant scripts to maven, and don't forget to feed the Tomcat, but, with sufficient struggle, you can still get to "Hello World 1.0" in Java.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
I'm sequencing alien DNA you insensitive clod.