Welcome!

Java IoT Authors: Yeshim Deniz, Liz McMillan, Zakia Bouachraoui, Elizabeth White, William Schmarzo

Related Topics: Java IoT

Java IoT: Article

Open Source Java? - Why on Earth Would I Want That?

Sun gave reporters an update on the planned release of Java and its associated tools under an open source license

Alan Williamson's Blog

(August 17, 2006) - This week at LinuxWorld Laurie Tolson gave reporters an update on the planned release of Java and its associated tools under an open source license.  By the end of the year, javac and the hot spot compiler will be released.  The precise license details haven't yet been announced yet - that is the part of the equation they are wrestling with the most since there are components within the JDK that aren't theirs to open source.  Politics and licenses aside, let us look at what this means for the humble Java developer, the troops in the trenches churning out code daily.

Java Dukey goes open source The first and natural concern is of course the dreading forking.  Forking is when two people make two different changes to the same code base resulting in an incompatibility with one another.  This scenario is Java armageddon - the one we all fear the most.  We have a small taste of this already when writing code for different versions of the JDK, but if you are careful and not always use the cutting edge API's then you're code will still happily run on legacy JVMs.  A good rule of thumb is to write for at least 2 versions behind the current release.  So with 1.6 about to make an appearance, you can safely play with the new tools with the 1.4 API.  Naturally this depends on your own application environment so its not a hard and fast rule by any stretch.

Another area where you may already be maintaining different code bases depending on the production system is with Microsoft J#.   Microsoft only got the rights up to Java 1.1 and if you code your Java application to that 1.1 API, then code will happily run on both the Microsoft .net and Java JVM runtimes.  So writing for different target systems is something developers have been use to for many years now, so should we be worried about the dreaded fork?

The problems faced so far by developers have largely been down to API changes, relying on methods/classes that may or may not exist on the production system.  These are relatively easy to spot with a good development environment.  For example, you can easily tell Eclipse to compile for only 1.4 with it doing all the checking to make sure you haven't lapsed into a 1.5 call.  But forking here could be more sinister than simple API misalignment.  What if you call a method and it does something completely different than you expect?

Sadly this isn't anything new to someone who has been coding Enterprise applications that are designed to run over a wide range of application servers.  Sure there is a standard JavaEE API that exists, but that is no assurance that your application will run fine on all application servers, as the interpretation of some of the API calls is down to the owner of the application server.  Even the standard, relatively small, Servlet API can produce many different results depending on the servlet container.

By forking the underlying JVM we now have a much greater potential for code to either not work or behave differently.  We are putting more responsibility onto the Java developer to either target a given runtime and code exclusively for that, or even worse, forcing them to test with different runtimes across different platforms.  Their job could get a whole lot messier.

We already have different runtimes available to us though, with BEA JRockit and IBM's runtime and these problems don't seem to have raised their ugly head.  The difference here is that these companies had to license the technology from Sun and be made to pass a stringent certification process before launching to the public at large.  In an open source world this certification restriction wouldn't be there.  People could easily hack the JDK to do something different and have no requirements to meet any test criteria.  They could simply use it as is.

A possible way around this would be to have Sun release the certification tools so other implementations of the JDK could be tested against it.  This may not necessarily test any new functionality that a developer added to the JDK, but it would make sure they didn't break anything that was suppose to work in the process.  This is far more important for wide acceptance.

Okay, so let us look at this from a point of view of hope.

What benefits can the developer get from an open source Java?  Take a  look at the JDK bug parade.  Take a look at the Top25 bugs.  Here is the biggest gain for the developer.

Some of the Top25 date back as far as 1999.  That is nearly 7 years a request/bug has sat there.  In an open source world, the 130 odd people that have voted to have low-level network support within Java could now potentially build it themselves and contribute it back to the core branch for potential inclusion.  At the moment, they have to wait until Sun dedicates coding resources to it.  It is obviously clear that Sun hasn't found the time in the last 7 years to address some of these!  Time to let someone else try.

There are many small bugs floating around that the community could easily tackle.  Many of the bugs/features are pure Java implementations with no native code required.  This opens up the potential number of contributors even further.  There could be a huge development boost to the community with a much faster release cycle.

Sun has to manage this carefully. If they can be shown to be responsible stewards of the code allowing contributions from others then the reason to fork the JVM will not be as great.  Why should you create your own JVM if your change can be incorporated into the main release and made available to you.  If you are that desparate for it and can't wait for a release, you can use the latest build from SVN/CVS.  Naturally I do not see Sun being the only committer on Java, they would merely be a member of a large group of committers.

On the whole I support the open sourcing of Java and its associated tools.  Sun is right to take this slowly and consult with all parties.  They only get one shot at this and once the genie is out of the bottle, it won't be wanting to go back in.

tags:      
links: digg this    del.icio.us  technorati

More Stories By Alan Williamson

Alan Williamson is widely recognized as an early expert on Cloud Computing, he is Co-Founder of aw2.0 Ltd, a software company specializing in deploying software solutions within Cloud networks. Alan is a Sun Java Champion and creator of OpenBlueDragon (an open source Java CFML runtime engine). With many books, articles and speaking engagements under his belt, Alan likes to talk passionately about what can be done TODAY and not get caught up in the marketing hype of TOMORROW. Follow his blog, http://alan.blog-city.com/ or e-mail him at cloud(at)alanwilliamson.org.

Comments (4)

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.


IoT & Smart Cities Stories
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...