|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?
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data shows "less than 10 percent of IoT developers are making enough to support a reasonably sized team....
Nov. 28, 2015 01:00 PM EST Reads: 469
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
Nov. 28, 2015 12:00 PM EST Reads: 330
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York and Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 17th Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world. The Internet of Things (IoT) is the most profound cha...
Nov. 28, 2015 12:00 PM EST Reads: 547
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, demonstrated examples of com...
Nov. 28, 2015 11:45 AM EST Reads: 399
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningful and actionable insights. In his session at @ThingsExpo, Paul Turner, Chief Marketing Officer at...
Nov. 28, 2015 11:15 AM EST Reads: 411
In his keynote at @ThingsExpo, Chris Matthieu, Director of IoT Engineering at Citrix and co-founder and CTO of Octoblu, focused on building an IoT platform and company. He provided a behind-the-scenes look at Octoblu’s platform, business, and pivots along the way (including the Citrix acquisition of Octoblu).
Nov. 28, 2015 11:00 AM EST Reads: 510
In his General Session at 17th Cloud Expo, Bruce Swann, Senior Product Marketing Manager for Adobe Campaign, explored the key ingredients of cross-channel marketing in a digital world. Learn how the Adobe Marketing Cloud can help marketers embrace opportunities for personalized, relevant and real-time customer engagement across offline (direct mail, point of sale, call center) and digital (email, website, SMS, mobile apps, social networks, connected objects).
Nov. 28, 2015 10:30 AM EST Reads: 308
We all know that data growth is exploding and storage budgets are shrinking. Instead of showing you charts on about how much data there is, in his General Session at 17th Cloud Expo, Scott Cleland, Senior Director of Product Marketing at HGST, showed how to capture all of your data in one place. After you have your data under control, you can then analyze it in one place, saving time and resources.
Nov. 28, 2015 10:00 AM EST Reads: 187
The Internet of Everything is re-shaping technology trends–moving away from “request/response” architecture to an “always-on” Streaming Web where data is in constant motion and secure, reliable communication is an absolute necessity. As more and more THINGS go online, the challenges that developers will need to address will only increase exponentially. In his session at @ThingsExpo, Todd Greene, Founder & CEO of PubNub, exploreed the current state of IoT connectivity and review key trends and technology requirements that will drive the Internet of Things from hype to reality.
Nov. 28, 2015 08:45 AM EST Reads: 433
Two weeks ago (November 3-5), I attended the Cloud Expo Silicon Valley as a speaker, where I presented on the security and privacy due diligence requirements for cloud solutions. Cloud security is a topical issue for every CIO, CISO, and technology buyer. Decision-makers are always looking for insights on how to mitigate the security risks of implementing and using cloud solutions. Based on the presentation topics covered at the conference, as well as the general discussions heard between sessions, I wanted to share some of my observations on emerging trends. As cyber security serves as a fou...
Nov. 28, 2015 08:45 AM EST Reads: 331
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now all corporate assets – people, objects, and spaces – can share information about themselves and thei...
Nov. 28, 2015 06:00 AM EST Reads: 242
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion is moderated by me, Dana Gardner, Principal Analyst at Interarbor Solutions.
Nov. 28, 2015 05:30 AM EST Reads: 730
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Nov. 28, 2015 05:00 AM EST Reads: 359
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true change and transformation possible.
Nov. 28, 2015 04:00 AM EST Reads: 538
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound effect on the world, and what should we expect to see over the next couple of years.
Nov. 28, 2015 03:30 AM EST Reads: 473
The cloud. Like a comic book superhero, there seems to be no problem it can’t fix or cost it can’t slash. Yet making the transition is not always easy and production environments are still largely on premise. Taking some practical and sensible steps to reduce risk can also help provide a basis for a successful cloud transition. A plethora of surveys from the likes of IDG and Gartner show that more than 70 percent of enterprises have deployed at least one or more cloud application or workload. Yet a closer inspection at the data reveals less than half of these cloud projects involve production...
Nov. 28, 2015 03:00 AM EST Reads: 482
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem" in this scenario: microservice A (releases daily) depends on a couple of additions to backend B (re...
Nov. 28, 2015 03:00 AM EST Reads: 450
Container technology is shaping the future of DevOps and it’s also changing the way organizations think about application development. With the rise of mobile applications in the enterprise, businesses are abandoning year-long development cycles and embracing technologies that enable rapid development and continuous deployment of apps. In his session at DevOps Summit, Kurt Collins, Developer Evangelist at Built.io, examined how Docker has evolved into a highly effective tool for application delivery by allowing increasingly popular Mobile Backend-as-a-Service (mBaaS) platforms to quickly crea...
Nov. 28, 2015 02:00 AM EST Reads: 361
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Day 2 Keynote at 17th Cloud Expo, Sandy Carter, IBM General Manager Cloud Ecosystem and Developers, and a Social Business Evangelist, wil...
Nov. 28, 2015 02:00 AM EST Reads: 579
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNub’s Data Stream Network.
Nov. 28, 2015 02:00 AM EST Reads: 328