Sponsored Links
How can Java rule the world?
Three key steps to Java's success
- Feedback
- Discuss
Page 2 of 3
Can Java rule the world? Possibly, maybe even probably. Java's widespread use requires that the Java community address the following three issues as quickly as possible.
Issue 1: Application development environments
There is an old joke in the Unix community: Unix documentation is written for people who already know the answers. In a similar vein, Java is very easy to use -- if you're an accomplished C++ programmer. Let's face it, Java is not exactly a 4GL.
In theory, developing in Java can be faster than C++ because it is much closer to an interpreted environment with class-level compiling and resolution of dependencies at runtime. The language is more accessible to developers than C++ because it eliminates the need to develop a specific pointer-based memory management scheme. Early indications show that accomplished C++ programmers can be two to three times more productive writing Java. However, the vast majority of people developing software are not C++ programmers.
As the revolution continues, vendors must provide a new set of development tools to make Java accessible to mainstream programmers who are willing to develop serious Internet or Intranet applications. Today, these mainstream developers write forms-based and database-centric applications in Visual Basic or some other 4GL. Connectivity to their information repository is very important. New tools must come to market quickly, tools that can rapidly make these developers more productive. The tools must be visual and easy to use, and hide the complexity of Java as much as possible.
Issue 2: Server support
Java already has the essence of a good client environment. Communication between clients and servers, however, is still primitive and remains limited to pipes, sockets, and file I/O. Java needs a clean, higher-level interface to databases and servers, like ODBC and OLE, to access persistent data. SunSoft offers one solution, a downloadable API for JDBC, a Java variant of ODBC. Meanwhile, Microsoft has announced the Internet Database Connector, which will allow existing ODBC applications to connect to their Internet Information Server. The jury has not yet reached a verdict on how well these and other interfaces will work. But one way or another, Java needs a higher-level interface to databases and legacy applications.
The real beauty of the complete Java environment is total independence of applications in a virtual machine. When there is better server support for clients and servers, it will be possible to make on-line modifications to applications written in Java. In other words, live applications may be modified while running. The result will be ideal: applications that run 24 hours a day, seven days a week.
Assuming that good server support appears quickly, the next problem involves developing rules for partitioning client and server executables. Until the typical network connection increases beyond 28.8 kbps, bandwidth will continue to be a problem. The remaining challenges include defining a server environment that minimizes the need for large applets on the client, defining a Java compression or buffering standard for transmission of larger applets, and distributing a robust set of standard applet libraries that will be available on every client system.
- Feedback
About Us | Advertise | Contact Us | Terms of Service/Privacy
Copyright, 2006-2008 Network World, Inc. All rights reserved.