But these advantages weren't of high importance for programmers when the Web was just emerging. Memory wasn't a huge issue, because Java applications tended to be run from a server, which tended to have a generous supply of memory. Nor was speed a critical issue. Most of the long start-up times that are associated with Java programs come from times needed to start a Java Virtual Machine (JVM) to run the program. But the application server software typically keeps the JVM running continuously, meaning that Java applications could be just as speedy as their C++ counterparts. "How often do you start your Web application? Once a day? Once a month?" Purdy asked.
Also, Java programs are better suited for running on multicore processors than C++ programs, Purdy argued. Programming for multicore processors can be a tedious task in C++. In contrast, Java's virtual machine handles the issue of which processors to use.
"All the benefits of C++ were not valuable. The strengths of Java are well-suited for this world," Purdy concluded. Though C and C++ are particularly suited for writing to a particular platform, crucial when developing an operating system or browser, such development efforts are not always called for. "How many browsers do we need?" he asked, rhetorically. "There are just not many places I need C++," he said.
The programming needs today promise a similar disruption as when Java supplanted C++, Purdy said. We are moving from a server-side architecture to what Purdy called a "thin server architecture," he said. He attributes this shift to a combination of cloud computing, HTML5 and mobile devices.
"These three things will conspire to be a perfect storm in our industry," Purdy said.
"Applications will shift from a very fat server model, where all the display logic is held on the server, to a much more thin server model where the display logic is in the browser itself," Purdy said. "Its communications with the server is with services and data."