Home ›

/var/opinion - Is GPL Java too little, too late?

Issue 158

From Issue #158
June 2007

Jun 01, 2007  By Nicholas Petreley
 in
Java is on its way to become mostly GPL but is it too late?
______________________

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Is this Editorial for Real

Anonymous's picture
Submitted by Anonymous (not verified) on Sat, 05/26/2007 - 01:51.

There are so many things wrong with this article, I don't know where to begin.

On the topic of WORA, though Java may aim for WORA, it falls short; wherever Sun or other commercial companies invest in R&D is what is supported. I don't see a rush of support for Mac OS 9, FreeBSD, or OS/2. With open source projects like Mono, it can be supported wherever the community desires to support, not at the whim of commercial companies. Additionally, many implementations, such as on HP-UX or other Unices, never quite work correctly for some APIs. In the Java community, it is often joked about WOTE (Write-Once, Test Everywhere).

When talking of platform-specific Java extension, what does he think AWT is? It has platform specific components to get it to work with GDI, Xorg, or Quartz. The argument about supporting USB or Firewire doesn't seem to hold water.

On the note of "Mono team is dead set on providing non-WORA functions by playing catchup with Windows API portion of .NET"? I'm not sure where he's coming from on this. Before to run Windows Forms, one had to use WINE, but it has been fully implement and is cross platform. Mud slinging to the Mono team is both ignorant and unsupportive of the spirit of open source and the whole bazaar concept.

He mentions that GPL-ization will solve all our problems but they can make them worse if there is no leadership in the Java community and we get tons of variant Java implementations.

In the end, he shares his struggles about Java, which sort of indicates his bias toward the Java language, and thus the Java platform. I love the concept of WORA, which is what .Net is about through ECMA standards, but I don't want to be forced or strong-armed particular language, especially IMHO a syntactically limited, gaudy or wordy language that takes pages to do small chores (ok, I'm a Perl programmer, what can I say). With .Net, you can choose your language, and inherit objects between languages on the CLR virtual machine, whereas Java VM only has mainly one language: Java.

Yo también considero que

Anonymous's picture
Submitted by Anonymous (not verified) on Mon, 07/09/2007 - 10:00.

Yo también considero que este articulo esta lleno de errores que solamente dejan al descubierto la falta de conocimiento por parte del autor acerca del proyecto MONO, de lo que es capaz de hacer MONO en la actualiad y el soporte que tiene para los diferentes SO que soporta.

MONO es una realidad y es multi plataforma eso es un hecho. El autor solamente refleja su profundo fanatismo y apego a java sin tener conocimiento de lo que critica.

En todo internet podemos ver muchos articulos como estos cuyo propósito es confundir y mal informar a los lectores acerca de los grandes esfuerzos y resultados exitosos que ha alcanzado MONO.

Mi consejo es que no se dejen llevar por el criterio de otras personas y que comprueben ustedes mismos los hechos....

Webcast
More Resources
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions