|By Joe Winchester||
|January 9, 2006 05:15 AM EST||
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.
|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,
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?
WebRTC is about the data channel as much as about video and audio conferencing. However, basically all commercial WebRTC applications have been built with a focus on audio and video. The handling of “data” has been limited to text chat and file download – all other data sharing seems to end with screensharing. What is holding back a more intensive use of peer-to-peer data? In her session at @ThingsExpo, Dr Silvia Pfeiffer, WebRTC Applications Team Lead at National ICT Australia, will look at different existing uses of peer-to-peer data sharing and how it can become useful in a live session to...
Oct. 7, 2015 11:30 AM EDT Reads: 515
SYS-CON Events announced today that Luxoft Holding, Inc., a leading provider of software development services and innovative IT solutions, has been named “Bronze Sponsor” of SYS-CON's @ThingsExpo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Luxoft’s software development services consist of core and mission-critical custom software development and support, product engineering and testing, and technology consulting.
Oct. 7, 2015 11:15 AM EDT Reads: 568
The enterprise is being consumerized, and the consumer is being enterprised. Moore's Law does not matter anymore, the future belongs to business virtualization powered by invisible service architecture, powered by hyperscale and hyperconvergence, and facilitated by vertical streaming and horizontal scaling and consolidation. Both buyers and sellers want instant results, and from paperwork to paperless to mindless is the ultimate goal for any seamless transaction. The sweetest sweet spot in innovation is automation. The most painful pain point for any business is the mismatch between supplies a...
Oct. 7, 2015 11:00 AM EDT Reads: 144
As a company adopts a DevOps approach to software development, what are key things that both the Dev and Ops side of the business must keep in mind to ensure effective continuous delivery? In his session at DevOps Summit, Mark Hydar, Head of DevOps, Ericsson TV Platforms, will share best practices and provide helpful tips for Ops teams to adopt an open line of communication with the development side of the house to ensure success between the two sides.
Oct. 7, 2015 11:00 AM EDT Reads: 555
There are so many tools and techniques for data analytics that even for a data scientist the choices, possible systems, and even the types of data can be daunting. In his session at @ThingsExpo, Chris Harrold, Global CTO for Big Data Solutions for EMC Corporation, will show how to perform a simple, but meaningful analysis of social sentiment data using freely available tools that take only minutes to download and install. Participants will get the download information, scripts, and complete end-to-end walkthrough of the analysis from start to finish. Participants will also be given the pract...
Oct. 7, 2015 10:21 AM EDT
As more and more data is generated from a variety of connected devices, the need to get insights from this data and predict future behavior and trends is increasingly essential for businesses. Real-time stream processing is needed in a variety of different industries such as Manufacturing, Oil and Gas, Automobile, Finance, Online Retail, Smart Grids, and Healthcare. Azure Stream Analytics is a fully managed distributed stream computation service that provides low latency, scalable processing of streaming data in the cloud with an enterprise grade SLA. It features built-in integration with Azur...
Oct. 7, 2015 10:00 AM EDT Reads: 736
NHK, Japan Broadcasting will feature upcoming @ThingsExpo Silicon Valley in a special IoT documentary which will be filmed on the expo floor November 3 to 5, 2015 in Santa Clara. NHK is the sole public TV network in Japan equivalent to BBC in UK and the largest in Asia with many award winning science and technology programs. Japanese TV is producing a documentary about IoT and Smart technology covering @ThingsExpo Silicon Valley. The program will be aired during the highest viewership season of the year that it will have a high impact in the industry through this documentary in Japan. The film...
Oct. 7, 2015 09:45 AM EDT Reads: 116
WebRTC: together these advances have created a perfect storm of technologies that are disrupting and transforming classic communications models and ecosystems. In his session at WebRTC Summit, Cary Bran, VP of Innovation and New Ventures at Plantronics and PLT Labs, will provide an overview of this technological shift, including associated business and consumer communications impacts, and opportunities it may enable, complement or entirely transform.
Oct. 7, 2015 09:30 AM EDT Reads: 674
WebRTC services have already permeated corporate communications in the form of videoconferencing solutions. However, WebRTC has the potential of going beyond and catalyzing a new class of services providing more than calls with capabilities such as mass-scale real-time media broadcasting, enriched and augmented video, person-to-machine and machine-to-machine communications. In his session at @ThingsExpo, Luis Lopez, CEO of Kurento, will introduce the technologies required for implementing these ideas and some early experiments performed in the Kurento open source software community in areas ...
Oct. 7, 2015 09:30 AM EDT Reads: 636
Who are you? How do you introduce yourself? Do you use a name, or do you greet a friend by the last four digits of his social security number? Assuming you don’t, why are we content to associate our identity with 10 random digits assigned by our phone company? Identity is an issue that affects everyone, but as individuals we don’t spend a lot of time thinking about it. In his session at @ThingsExpo, Ben Klang, Founder & President of Mojo Lingo, will discuss the impact of technology on identity. Should we federate, or not? How should identity be secured? Who owns the identity? How is identity ...
Oct. 7, 2015 08:30 AM EDT Reads: 421
Developing software for the Internet of Things (IoT) comes with its own set of challenges. Security, privacy, and unified standards are a few key issues. In addition, each IoT product is comprised of at least three separate application components: the software embedded in the device, the backend big-data service, and the mobile application for the end user's controls. Each component is developed by a different team, using different technologies and practices, and deployed to a different stack/target - this makes the integration of these separate pipelines and the coordination of software upd...
Oct. 7, 2015 08:00 AM EDT Reads: 141
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Oct. 7, 2015 06:45 AM EDT Reads: 741
WebRTC converts the entire network into a ubiquitous communications cloud thereby connecting anytime, anywhere through any point. In his session at WebRTC Summit,, Mark Castleman, EIR at Bell Labs and Head of Future X Labs, will discuss how the transformational nature of communications is achieved through the democratizing force of WebRTC. WebRTC is doing for voice what HTML did for web content.
Oct. 7, 2015 06:15 AM EDT Reads: 1,337
The broad selection of hardware, the rapid evolution of operating systems and the time-to-market for mobile apps has been so rapid that new challenges for developers and engineers arise every day. Security, testing, hosting, and other metrics have to be considered through the process. In his session at Big Data Expo, Walter Maguire, Chief Field Technologist, HP Big Data Group, at Hewlett-Packard, will discuss the challenges faced by developers and a composite Big Data applications builder, focusing on how to help solve the problems that developers are continuously battling.
Oct. 7, 2015 04:00 AM EDT Reads: 454
Nowadays, a large number of sensors and devices are connected to the network. Leading-edge IoT technologies integrate various types of sensor data to create a new value for several business decision scenarios. The transparent cloud is a model of a new IoT emergence service platform. Many service providers store and access various types of sensor data in order to create and find out new business values by integrating such data.
Oct. 7, 2015 03:30 AM EDT Reads: 459
SYS-CON Events announced today that IBM Cloud Data Services has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. IBM Cloud Data Services offers a portfolio of integrated, best-of-breed cloud data services for developers focused on mobile computing and analytics use cases.
Oct. 6, 2015 10:00 PM EDT Reads: 666
In his session at @ThingsExpo, Tony Shan, Chief Architect at CTS, will explore the synergy of Big Data and IoT. First he will take a closer look at the Internet of Things and Big Data individually, in terms of what, which, why, where, when, who, how and how much. Then he will explore the relationship between IoT and Big Data. Specifically, he will drill down to how the 4Vs aspects intersect with IoT: Volume, Variety, Velocity and Value. In turn, Tony will analyze how the key components of IoT influence Big Data: Device, Connectivity, Context, and Intelligence. He will dive deep to the matrix...
Oct. 6, 2015 08:00 PM EDT Reads: 318
When it comes to IoT in the enterprise, namely the commercial building and hospitality markets, a benefit not getting the attention it deserves is energy efficiency, and IoT’s direct impact on a cleaner, greener environment when installed in smart buildings. Until now clean technology was offered piecemeal and led with point solutions that require significant systems integration to orchestrate and deploy. There didn't exist a 'top down' approach that can manage and monitor the way a Smart Building actually breathes - immediately flagging overheating in a closet or over cooling in unoccupied ho...
Oct. 6, 2015 05:00 PM EDT Reads: 262
SYS-CON Events announced today that Cloud Raxak has been named “Media & Session Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Raxak Protect automates security compliance across private and public clouds. Using the SaaS tool or managed service, developers can deploy cloud apps quickly, cost-effectively, and without error.
Oct. 6, 2015 04:40 PM EDT Reads: 120
Scott Guthrie's keynote presentation "Journey to the intelligent cloud" is a must view video. This is from AzureCon 2015, September 29, 2015 I have reproduced some screen shots in case you are unable to view this long video for one reason or another. One of the highlights is 3 datacenters coming on line in India.
Oct. 6, 2015 02:00 PM EDT Reads: 239