Welcome!

Java Authors: Carmen Gonzalez, Victoria Livschitz, Pat Romanski, Liz McMillan, Larry Dragich

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
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.
An entirely new security model is needed for the Internet of Things, or is it? Can we save some old and tested controls for this new and different environment? In his session at @ThingsExpo, New York's at the Javits Center, Davi Ottenheimer, EMC Senior Director of Trust, reviewed hands-on lessons with IoT devices and reveal a new risk balance you might not expect. Davi Ottenheimer, EMC Senior Director of Trust, has more than nineteen years' experience managing global security operations and assessments, including a decade of leading incident response and digital forensics. He is co-author of t...
The Internet of Things will greatly expand the opportunities for data collection and new business models driven off of that data. In her session at @ThingsExpo, Esmeralda Swartz, CMO of MetraTech, discussed how for this to be effective you not only need to have infrastructure and operational models capable of utilizing this new phenomenon, but increasingly service providers will need to convince a skeptical public to participate. Get ready to show them the money!
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges. In his session at @ThingsExpo, Jeff Kaplan, Managing Director of THINKstrategies, will examine why IT must finally fulfill its role in support of its SBUs or face a new round of...
One of the biggest challenges when developing connected devices is identifying user value and delivering it through successful user experiences. In his session at Internet of @ThingsExpo, Mike Kuniavsky, Principal Scientist, Innovation Services at PARC, described an IoT-specific approach to user experience design that combines approaches from interaction design, industrial design and service design to create experiences that go beyond simple connected gadgets to create lasting, multi-device experiences grounded in people's real needs and desires.
Enthusiasm for the Internet of Things has reached an all-time high. In 2013 alone, venture capitalists spent more than $1 billion dollars investing in the IoT space. With "smart" appliances and devices, IoT covers wearable smart devices, cloud services to hardware companies. Nest, a Google company, detects temperatures inside homes and automatically adjusts it by tracking its user's habit. These technologies are quickly developing and with it come challenges such as bridging infrastructure gaps, abiding by privacy concerns and making the concept a reality. These challenges can't be addressed w...
The Domain Name Service (DNS) is one of the most important components in networking infrastructure, enabling users and services to access applications by translating URLs (names) into IP addresses (numbers). Because every icon and URL and all embedded content on a website requires a DNS lookup loading complex sites necessitates hundreds of DNS queries. In addition, as more internet-enabled ‘Things' get connected, people will rely on DNS to name and find their fridges, toasters and toilets. According to a recent IDG Research Services Survey this rate of traffic will only grow. What's driving t...
Connected devices and the Internet of Things are getting significant momentum in 2014. In his session at Internet of @ThingsExpo, Jim Hunter, Chief Scientist & Technology Evangelist at Greenwave Systems, examined three key elements that together will drive mass adoption of the IoT before the end of 2015. The first element is the recent advent of robust open source protocols (like AllJoyn and WebRTC) that facilitate M2M communication. The second is broad availability of flexible, cost-effective storage designed to handle the massive surge in back-end data in a world where timely analytics is e...
Scott Jenson leads a project called The Physical Web within the Chrome team at Google. Project members are working to take the scalability and openness of the web and use it to talk to the exponentially exploding range of smart devices. Nearly every company today working on the IoT comes up with the same basic solution: use my server and you'll be fine. But if we really believe there will be trillions of these devices, that just can't scale. We need a system that is open a scalable and by using the URL as a basic building block, we open this up and get the same resilience that the web enjoys.
We are reaching the end of the beginning with WebRTC, and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) i...
"Matrix is an ambitious open standard and implementation that's set up to break down the fragmentation problems that exist in IP messaging and VoIP communication," explained John Woolf, Technical Evangelist at Matrix, in this SYS-CON.tv interview at @ThingsExpo, held Nov 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA.
How do APIs and IoT relate? The answer is not as simple as merely adding an API on top of a dumb device, but rather about understanding the architectural patterns for implementing an IoT fabric. There are typically two or three trends: Exposing the device to a management framework Exposing that management framework to a business centric logic Exposing that business layer and data to end users. This last trend is the IoT stack, which involves a new shift in the separation of what stuff happens, where data lives and where the interface lies. For instance, it's a mix of architectural styles ...
Cultural, regulatory, environmental, political and economic (CREPE) conditions over the past decade are creating cross-industry solution spaces that require processes and technologies from both the Internet of Things (IoT), and Data Management and Analytics (DMA). These solution spaces are evolving into Sensor Analytics Ecosystems (SAE) that represent significant new opportunities for organizations of all types. Public Utilities throughout the world, providing electricity, natural gas and water, are pursuing SmartGrid initiatives that represent one of the more mature examples of SAE. We have s...
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at @ThingsExpo, Robin Raymond, Chief Architect at Hookflash, will walk through the shifting landscape of traditional telephone and voice services ...
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, discussed single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example t...
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at Internet of @ThingsExpo, James Kirkland, Chief Architect for the Internet of Things and Intelligent Systems at Red Hat, described how to revolutioniz...
Bit6 today issued a challenge to the technology community implementing Web Real Time Communication (WebRTC). To leap beyond WebRTC’s significant limitations and fully leverage its underlying value to accelerate innovation, application developers need to consider the entire communications ecosystem.
The definition of IoT is not new, in fact it’s been around for over a decade. What has changed is the public's awareness that the technology we use on a daily basis has caught up on the vision of an always on, always connected world. If you look into the details of what comprises the IoT, you’ll see that it includes everything from cloud computing, Big Data analytics, “Things,” Web communication, applications, network, storage, etc. It is essentially including everything connected online from hardware to software, or as we like to say, it’s an Internet of many different things. The difference ...
Cloud Expo 2014 TV commercials will feature @ThingsExpo, which was launched in June, 2014 at New York City's Javits Center as the largest 'Internet of Things' event in the world.
SYS-CON Events announced today that Windstream, a leading provider of advanced network and cloud communications, has been named “Silver Sponsor” of SYS-CON's 16th International Cloud Expo®, which will take place on June 9–11, 2015, at the Javits Center in New York, NY. Windstream (Nasdaq: WIN), a FORTUNE 500 and S&P 500 company, is a leading provider of advanced network communications, including cloud computing and managed services, to businesses nationwide. The company also offers broadband, phone and digital TV services to consumers primarily in rural areas.