Welcome!

Java Authors: Patrick Carey, Liz McMillan, Elizabeth White, Srinivasan Sundara Rajan, Pat Romanski

Related Topics: Java, SYS-CON MEDIA

Java: Article

i-Technology Viewpoint: Java's Not Evolving Fast Enough

Do Strongly Typed APIs Help Ensure Java's Survival or Extinction, Asks Java Developer's Journal's Joe Winchester

A programming API represents a documented contract between a function that provides some kind of computing service and those who wish to use it. In Java, once an API is used there is a physical contract between the two that the compiler and JVM enforce. If at some point in the future the author of the API wishes to make changes, they are limited in scope; if the author renames methods or removes arguments, programs that are bound to the previous signature will no longer run. The change can be published with the new version of the class library or framework so that users can upgrade their code; however, in many cases this isn't a viable option. It may be that the system that used the old API is no longer being worked on by a development team and is considered stable, or that the release cycle of the now broken system is dependent on other circumstances that prevent it from being upgraded.

No API can be got right the first time, irrespective of how many specifications, architecture meetings, and examples take place prior to its release. The whole idea of launching a set of class libraries and Javadocs onto the world as being the eternal way of doing something goes against the whole philosophy of agile programming. One of the principles of extreme programming is that a good program is built flexibly and in a fluid state; at each stage the feedback loop of usage and reconstruction means that the right solution is arrived at by accident rather than by design. This is akin to evolution, whereby variations in a species arise by random mutation and are mixed in offspring to create new individuals. The fittest varieties survive whatever the environment provides and the cycle continues, allowing the species to adapt and evolve.

The Java language has maintained its API over many releases so a program that is compiled on 1.2 will run unchanged on a Java 5 runtime environment The benefit of this is that older Java programs remain functional on modern JREs; however, it comes at a price. The language now contains a plethora of deprecated classes and methods, new features are sometimes sacrificed to ensure backward compatibility, and the evolution of Java is hindered and held back. The class java.util.Date, for example, has more public deprecated methods than non-deprecated ones. Not a lot has changed in the domain model of Dates since the Gregorian calendar was introduced in 1582, and this ratio of legacy to current API is a sign that code change is a natural flux that occurs during its usage.

In nature the extinction of a species is not a gradual thing but comes in waves. Punctuated Equilibrium describes an effect whereby the environment remains fairly static for a while and then a huge amount of change occurs in a small amount of time. These boundaries are mass extinctions that not only cause many species to die out, but are also the event that allows others to flourish and fill the void left by the departing ones. To a certain extent Java benefited from this back in 1995, when it was born out of a combination of the best ideas of C++ and Smalltalk; the catastrophic meteorite striking at the time being the Internet and demand for heterogeneous networked computing.

What worries me 10 years later is that I don't believe Java is evolving fast enough, and that strong typing to antiquated APIs are holding it back. XML won over a slew of competing technologies for program-to-program communication transport because it is text based, allowing it to be read by heterogeneous end points (as opposed to alternatives like CORBA IDL or other binary RPCs). XML is also flexible in its typing, because tags can be declared as optional and new tags can be introduced in a message without breaking callers using the older format. While Java has done well as an enterprise language in the application server space, this is largely due to the fact that the big names of IT backed it rather than any inherent feature of the language. Languages such as Ruby and Perl have grown tremendously in the past few years and now command a sizeable portion of application development.

If Java is to remain at the forefront of technology for the next 10 years, it must find a better way to evolve. It needs to find a way of decoupling API calls between internal code and external blocks, perhaps even introducing soft typing calls across program boundaries or having flexible message transport across modules. While XML parsing functionality is now included in a Java runtime by default, it feels very shoehorned into place when compared with how .NET has done the same integration. Older languages like COBOL or RPG, as well as Visual Basic, include the concept of structures into a program definition that can be externalized, and having Java include a slew of JARs and runtime bolt ons to do simple XML parsing seems a missed opportunity to embrace the technology.

Becoming strong enough to do battle with Microsoft, the T-Rex of computing, may have fared well for Java in the past, but at the expense of what it has now become and how quickly it can keep up with change and the legacy it has created. I fear that unless a fundamental change to the language is made that allows more flexibility in binding between functional units, between and across JVM boundaries, Java will be a victim of the same fate as the behemoths it fights in the IT tar pit. Survival against change - whether in nature, technology, or business - is determined by ones ability to adapt. Java needs to move forward by being more agile. As the language grows with more and more APIs and divisions, it runs the risk of losing sight of the finish line, while smaller and nimbler technologies become more ubiquitous. When the next IT meteor strikes, Java must be the fastest to adapt if it is to survive and grow over the next 10 years.

More Stories By Joe Winchester

Joe Winchester, Editor-in-Chief of Java Developer's Journal, was formerly JDJ's longtime Desktop Technologies Editor and is a software developer working on development tools for IBM in Hursley, UK.

Comments (12) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Byron Estes 01/12/06 01:10:10 PM EST

I wonder if this discussion might be more productive if someone offered a particular concrete situation they encountered that reflects the limitations that they feel are holding Java back. If the author reads this, I would call on him to supply a specific instance that would allow us to get away from opinions, and rhetoric. Discussing an example in this way (...more likely a series of examples) will probably help us get closer to understanding each others points. Given that understanding we could then expand back out to more broader discussion of he subject. Thoughts?

mel martinez 01/12/06 12:56:12 AM EST

I personally kind of hate comparisons between XML and Java. They are two totally different kinds of tools that are used in totally different ways. To suggest that XML (a spectrum of markup languages) is somehow 'more flexible' than Java (an OO programming language) is meaningless. They are both flexible and both rigid in totally different ways. An xml schema can be just as rigid and inflexible in the face of future changes as a strongly typed java interface signature. The correlary to the deprecated method in a java api is a long list of 'optional' attributes in a tag definition. I would suggest that the vast majority of problems that 'limit flexibility' in Java (or any programming language) have more to do with design patterns - too many anti-patterns and not enough use of good patterns. That is not to say that there could not be differences in the language that would help encourage good patterns and discourage falling into bad patterns. But even without fundamental changes to the language, much of that could be achieved through better development tools that better guard the developer from falling into anti-pattern traps and encourage the use of good patterns that facilitate future flexibility.

Joe Winchester 01/11/06 07:05:13 PM EST

The point about strong typing vs. weak typing is not trying to bring back memory spaces as a way of passing program arguments. Typing is good for the compiler, however it is too inflexible. XML has a benfit in its design which is that the data and the meaning of the data are combined, so it can be partially complete, pieces ignored by the receipient if it doesn't understand it. I'm not advocating XML as a transport between Java program modules, I just think we need something less brittle than what we have now that can't accomodate change. This is similar to how the Java XMLEncoder is superior to binary serialization, because it can deal with updates without everything breaking

mel martinez 01/10/06 06:46:49 PM EST

Somehow, I doubt it is the fact that java is a strongly typed language will be the determining factor in its long-term success. There are much bigger issues, primarily whether java is percieved by customers to be an appropriate tool for the solution of their real world problems. The number of deprecated calls in some of the APIs does not in my experience jump to the forefront of things to consider when comparing development tools and languages. Yes, it is symptomatic of some things that are going on, but it isn't imho a deal breaker with most folks. The fact is, the quality of development tools available and the ubiquity of experience of developers with a language and the associated tools will tend to be the predominant factors. I'm not saying here that java is destined to succeed (whatever that means) or not with or without faster adoption of changes. I just don't think that strongly typed signatures are the major negative issue the article makes them out to be. There are, after all, real benefits to a strongly typed language.

Gary Renner 01/10/06 04:42:10 PM EST

I could not disagree more with this article. Maybe you have to be as old as I am to remember the days before strong type checking. The lack of strong type checking in assembler, c and basic lead to very slow development process due to bugs that would have easily been detected in java, Modula 2, or Pascal. To me, you are advocating a change back to the bad old days. Elimination of strong type checking will not solve the problem of brittleness of code. Even eliminating type checking completely will not solve the real issues that impede software state of the art. To reach the next state in software development, we have to be able to stand on previous developers shoulders - that means reusability and modularity. What is the biggest impediment to reusability? From my perspective, it is the proliferation of computer languages. How many times do we have to spend software $ rewriting quicksort when we could be using those dollars to write more intelligent database management systems?

You mention XML as a positive thing because it is text based. That would only be true if their were fewer character sets than there are representations for fundamental types like float and integer. Last time I looked, this was not the case. The number of character sets is roughly the number of standards (ascii, ebcdic, unicode, etc.) times the number of languages (english, japanese, etc.) - there is plenty of room for lack of compatibility and brittleness in the XML world. Also, XML only addresses a very limited universe: fundamental data types. It does not deal with: semantics, complex objects (e.g. multimedia), mobile code, security, inheritance etc and most of all, performance. I see XML as negative evolution because these problems are already solved in JVM byte code. To call XML portable would be to mis-characterize it - the standards and tooling are so complex, they really exist on only 2 platforms: Java and .net. Even those platforms are not exactly compatible.

Jim Babka 01/10/06 01:45:28 PM EST

At some point in the evolution of any API, you hear someone calling for a do-over. They say, "it's too hard to evolve," or "nobody uses those methods anymore." While there might be the best of reasons for changing, incompatible changes to any API cause much more confusion and strife than living within the boundaries of compatibility.

If such a thing occurred to Java, it would kill the language. All the new cool features would go into "Java 3", while the entire corporate world stayed on Java 2, and thus the tools would also remain on Java 2 (it's a chicken-and-egg problem that we've seen numerous times before). Eventually, anyone who got fed up with the lack of new features in Java 2 would decide to move to a new language, and the lack of tools for Java 3 would be a big strike against it.

No, painful as it sometimes is, compatibility must be preserved. Once you decide you can break compatibility, you fracture the entire user landscape, and Java can't afford that.

Byron Estes 01/10/06 01:04:39 PM EST

Certainly, maintaining interfaces that supply services to support many applications is not easy and they do evolve over time. This form of distributed computing has advantages that do not come without a cost, but I would contend that the problems the author of this article is citing are as much or more a problem with how we design the interfaces as they are with the implementation. I agree, that you'll never get the interface right the first time and yes it will most certainly change over time. What I am talking about is tight cohesion and loose coupling. Nothing magical, but not always practiced. My experience has been that as long as you keep the services loosely coupled and start with some flexible command pattern super classes, that you can deal with lots of these issues. Is it perfect, no. I still, however, remember the headaches and hard to find runtime bugs that can be introduced through a lack of strong data typing and the use of pointers to blocks of memory. I have programmed in everything from mainframe assembler to Java (...and .NET). I still would rather use it than other language/platform I've ever encountered.

Yakov Fain 01/09/06 09:11:50 AM EST

>The class java.util.Date, for example, has more public deprecated methods than non-deprecated ones.

IMHO, Sun should come up with a light-footprint version of JVM that does not support deprecated version of methods. This JVM should not replace the existing one, but present an option to the recently developed Java applications

DoubtingThomas 01/09/06 07:03:39 AM EST

If Apple couldn't withstand the digital gottedamerung that is Microsoft, then what makes anyone think that Java can?

rolsen 01/09/06 06:55:12 AM EST

Rhe buzz at the last software conference I attended, a conference previously full of Java developers and talk, was all about Ruby. The web is filling up with talk about the R word. Yesterday an old friend of mine IM'ed me to say that he had a new job and his boss wants him to do this Rails thing and did I think it was for real.

Not Gone Yet 01/09/06 06:40:43 AM EST

>> Survival against change - whether in nature,
>> technology, or business - is determined by one's
>> ability to adapt. Java needs to move forward by
>> being more agile

Java's popularity might be declining, but the concept of its JVM sure isn't. And I'll be using Java for a considerable amount of time in the future anyway.

queZZtion 01/09/06 06:32:07 AM EST

||| If Java is to remain at the forefront of technology for the next 10 years, it ... needs to find a way of decoupling API calls between internal code and external blocks, perhaps even introducing soft typing calls across program boundaries or having flexible message transport across modules. |||

It will be interesting to see what Sun itself has to say in response to this. I am assuming JDJ has invited a response?

@ThingsExpo Stories
"People are a lot more knowledgeable about APIs now. There are two types of people who work with APIs - IT people who want to use APIs for something internal and the product managers who want to do something outside APIs for people to connect to them," explained Roberto Medrano, Executive Vice President at SOA Software, in this SYS-CON.tv interview at Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
“In the past year we've seen a lot of stabilization of WebRTC. You can now use it in production with a far greater degree of certainty. A lot of the real developments in the past year have been in things like the data channel, which will enable a whole new type of application," explained Peter Dunkley, Technical Director at Acision, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
Nigeria has the largest economy in Africa, at more than US$500 billion, and ranks 23rd in the world. A recent re-evaluation of Nigeria's true economic size doubled the previous estimate, and brought it well ahead of South Africa, which is a member (unlike Nigeria) of the G20 club for political as well as economic reasons. Nigeria's economy can be said to be quite diverse from one point of view, but heavily dependent on oil and gas at the same time. Oil and natural gas account for about 15% of Nigera's overall economy, but traditionally represent more than 90% of the country's exports and as...
The Internet of Things is a misnomer. That implies that everything is on the Internet, and that simply should not be - especially for things that are blurring the line between medical devices that stimulate like a pacemaker and quantified self-sensors like a pedometer or pulse tracker. The mesh of things that we manage must be segmented into zones of trust for sensing data, transmitting data, receiving command and control administrative changes, and peer-to-peer mesh messaging. In his session at @ThingsExpo, Ryan Bagnulo, Solution Architect / Software Engineer at SOA Software, focused on desi...
"At our booth we are showing how to provide trust in the Internet of Things. Trust is where everything starts to become secure and trustworthy. Now with the scaling of the Internet of Things it becomes an interesting question – I've heard numbers from 200 billion devices next year up to a trillion in the next 10 to 15 years," explained Johannes Lintzen, Vice President of Sales at Utimaco, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
"For over 25 years we have been working with a lot of enterprise customers and we have seen how companies create applications. And now that we have moved to cloud computing, mobile, social and the Internet of Things, we see that the market needs a new way of creating applications," stated Jesse Shiah, CEO, President and Co-Founder of AgilePoint Inc., in this SYS-CON.tv interview at 15th Cloud Expo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Events announced today that Gridstore™, the leader in hyper-converged infrastructure purpose-built to optimize Microsoft workloads, will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY. Gridstore™ is the leader in hyper-converged infrastructure purpose-built for Microsoft workloads and designed to accelerate applications in virtualized environments. Gridstore’s hyper-converged infrastructure is the industry’s first all flash version of HyperConverged Appliances that include both compute and storag...
Today’s enterprise is being driven by disruptive competitive and human capital requirements to provide enterprise application access through not only desktops, but also mobile devices. To retrofit existing programs across all these devices using traditional programming methods is very costly and time consuming – often prohibitively so. In his session at @ThingsExpo, Jesse Shiah, CEO, President, and Co-Founder of AgilePoint Inc., discussed how you can create applications that run on all mobile devices as well as laptops and desktops using a visual drag-and-drop application – and eForms-buildi...
We certainly live in interesting technological times. And no more interesting than the current competing IoT standards for connectivity. Various standards bodies, approaches, and ecosystems are vying for mindshare and positioning for a competitive edge. It is clear that when the dust settles, we will have new protocols, evolved protocols, that will change the way we interact with devices and infrastructure. We will also have evolved web protocols, like HTTP/2, that will be changing the very core of our infrastructures. At the same time, we have old approaches made new again like micro-services...
Code Halos - aka "digital fingerprints" - are the key organizing principle to understand a) how dumb things become smart and b) how to monetize this dynamic. In his session at @ThingsExpo, Robert Brown, AVP, Center for the Future of Work at Cognizant Technology Solutions, outlined research, analysis and recommendations from his recently published book on this phenomena on the way leading edge organizations like GE and Disney are unlocking the Internet of Things opportunity and what steps your organization should be taking to position itself for the next platform of digital competition.
The 3rd International Internet of @ThingsExpo, co-located with the 16th International Cloud Expo - to be held June 9-11, 2015, at the Javits Center in New York City, NY - announces that its Call for Papers is now open. The Internet of Things (IoT) is the biggest idea since the creation of the Worldwide Web more than 20 years ago.
As the Internet of Things unfolds, mobile and wearable devices are blurring the line between physical and digital, integrating ever more closely with our interests, our routines, our daily lives. Contextual computing and smart, sensor-equipped spaces bring the potential to walk through a world that recognizes us and responds accordingly. We become continuous transmitters and receivers of data. In his session at @ThingsExpo, Andrew Bolwell, Director of Innovation for HP's Printing and Personal Systems Group, discussed how key attributes of mobile technology – touch input, sensors, social, and ...
In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect at GE, and Ibrahim Gokcen, who leads GE's advanced IoT analytics, focused on the Internet of Things / Industrial Internet and how to make it operational for business end-users. Learn about the challenges posed by machine and sensor data and how to marry it with enterprise data. They also discussed the tips and tricks to provide the Industrial Internet as an end-user consumable service using Big Data Analytics and Industrial Cloud.
Things are being built upon cloud foundations to transform organizations. This CEO Power Panel at 15th Cloud Expo, moderated by Roger Strukhoff, Cloud Expo and @ThingsExpo conference chair, addressed the big issues involving these technologies and, more important, the results they will achieve. Rodney Rogers, chairman and CEO of Virtustream; Brendan O'Brien, co-founder of Aria Systems, Bart Copeland, president and CEO of ActiveState Software; Jim Cowie, chief scientist at Dyn; Dave Wagstaff, VP and chief architect at BSQUARE Corporation; Seth Proctor, CTO of NuoDB, Inc.; and Andris Gailitis, C...
Building low-cost wearable devices can enhance the quality of our lives. In his session at Internet of @ThingsExpo, Sai Yamanoor, Embedded Software Engineer at Altschool, provided an example of putting together a small keychain within a $50 budget that educates the user about the air quality in their surroundings. He also provided examples such as building a wearable device that provides transit or recreational information. He then reviewed the resources available to build wearable devices at home including open source hardware, the raw materials required and the options available to power s...
There's Big Data, then there's really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at Big Data Expo®, Hannah Smalltree, Director at Treasure Data, discussed how IoT, Big Data and deployments are processing massive data volumes from wearables, utilities and other machines...
"There is a natural synchronization between the business models, the IoT is there to support ,” explained Brendan O'Brien, Co-founder and Chief Architect of Aria Systems, in this SYS-CON.tv interview at the 15th International Cloud Expo®, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
SYS-CON Media announced that Splunk, a provider of the leading software platform for real-time Operational Intelligence, has launched an ad campaign on Big Data Journal. Splunk software and cloud services enable organizations to search, monitor, analyze and visualize machine-generated big data coming from websites, applications, servers, networks, sensors and mobile devices. The ads focus on delivering ROI - how improved uptime delivered $6M in annual ROI, improving customer operations by mining large volumes of unstructured data, and how data tracking delivers uptime when it matters most.
In this Women in Technology Power Panel at 15th Cloud Expo, moderated by Anne Plese, Senior Consultant, Cloud Product Marketing at Verizon Enterprise, Esmeralda Swartz, CMO at MetraTech; Evelyn de Souza, Data Privacy and Compliance Strategy Leader at Cisco Systems; Seema Jethani, Director of Product Management at Basho Technologies; Victoria Livschitz, CEO of Qubell Inc.; Anne Hungate, Senior Director of Software Quality at DIRECTV, discussed what path they took to find their spot within the technology industry and how do they see opportunities for other women in their area of expertise.
While great strides have been made relative to the video aspects of remote collaboration, audio technology has basically stagnated. Typically all audio is mixed to a single monaural stream and emanates from a single point, such as a speakerphone or a speaker associated with a video monitor. This leads to confusion and lack of understanding among participants especially regarding who is actually speaking. Spatial teleconferencing introduces the concept of acoustic spatial separation between conference participants in three dimensional space. This has been shown to significantly improve comprehe...