7 64 Bits | Java

Java 6 had a fatal flaw: its memory limit. "I can only hold 4 gigs of the world," it would whisper, its fans spinning sadly. "Beyond that... there is only OutOfMemoryError ."

"Thank you," the packets say.

switch (command) { case "START": engine.begin(); break; case "STOP": engine.halt(); break; case "STATUS": reporter.show(); break; default: logger.warn("Unknown command"); } The bytecode hummed. The router, for the first time, executed string branching as efficiently as integers. Traffic flowed. Deep in the dungeons of the filesystem, there was a leak. Not a memory leak—a resource leak . A database connection had been opened in the dark ages and never closed. It was a zombie connection, eating cursors and spitting out IOException . java 7 64 bits

It is the bridge. The one that first broke the 4GB wall. The one that taught developers to close their resources automatically. The one that said, "You can switch on a string now." Java 6 had a fatal flaw: its memory limit

Java 7 smiled. "Size is a small price for power. Watch." there is only OutOfMemoryError