I signed the petition to Open Source the JavaFX Platform. I think the benefits of Open SourcingJavaFX can be huge, both for Oracle and the JavaFX community.The example of Glassfish, where the open community-approach leads tohigh quality software while still allowing a commercialmodel, can be followed by JavaFX.
First of all, I should stress that I’m not in a position to dictate whatOracle should or should not do with JavaFX. They inherited the platformthrough their acquisition of Sun, and they have spent lots of resources inJavaFX.The idea of the petition is rather to convince Oracle that it would bein the best interest of Oracle, the JavaFX developers and the Internetin general to open-source the JavaFX platform.
The ideas behind JavaFX are great: use the power, the maturity and theavailability of the Java platform to create a client-side language thatallows the rapid creation of highly interactive and rich client applications,that run on all Java-based systems. At this moment, JavaFX is the onlyRIA platform that is entirely based on the Java platform.
I see a growing interest from Java Enterprise developers in client-sidedevelopment and vice versa. Without JavaFX, these Java (Enterprise)developers have to choose between a non-Java based RIA or a fewthousands specific web-based frameworks for their client development.With JavaFX, it becomes much easier for them to create rich and interactiveclient-applications.
JavaFX entered the RIA market pretty late. Competition from Flex andSilverlight was already on the market, attracting developers and companies.In order for JavaFX to be successful, time to market is a crucial factor.
The JavaFX platform specification is already pretty ok, but the runtimeports need to be improved. I remember from my first Java-days (in 1995)the problems with lack of Java support on different platforms, and thatwas exactly the reason I joined the Blackdown team. We had to sign alicense with Sun Microsystems, received the source code, and we couldwork on a port that we could distribute. While this was still a ratherclosed process, it allowed third party enthusiasts to speed up theavailability of Java.
A great example of how open-sourcing a project can enhance its qualityand acceptance is Glassfish.The Glassfish project was announced at JavaOne 2005 as the open sourceReference Implementation of the Java Enterprise specification.It is a huge project, and Sun and Oracle have spent lots of resources init. It is difficult to quantify the community input, but there are manypeople outside Sun/Oracle involved with Glassfish by writing/reviewingcode, documentation, working on the Quality Assurance (e.g. via FishCat),working with early access versions etc.
The result of the combination Open-Source with “backed-by-a-company” isin this case a great Application Server, leading edge and still verymature, easy to use and highly configurable.
As a developer, one of the main benefits of the Glassfish community is thatI can easily debug issues I run into. If those issues are Glassfish-related,I can report this to the community, I can write a patch myself and commitit to the community. And, very important, while waiting for a releasedversion that contains a fix, I can patch my own version and run mycustomer projects that require the fix.
I would recommend a similar approach for JavaFX. Strategic and commercialdecisions probably belong to Oracle. But opening the Runtime (includingports to mobile and TV) can create a boost in JavaFX quality andenthusiasm. It is important to have a company that is backing the development, and that provides steering and infrastructure. It is also important to have enthusiastic people in the community that are allowed to contribute and to enhance the quality and adoption.
Johan's blog 