Eduardo Pelegri-Llopart's Blog

OpenSourcing Java and Language Design...

I think that the OpenSourcing of the Java Platform may very well lead to a new wave of Programming Language designs. For example, check out Chris Oliver's Postings on F3 and then check this Language Overview. Don't be confused by the examples that emphasize only the GUI abilities of the language - it is much more than that. Pretty cool, eh? Now, combine that with a widely available JVM and Java Platform... and add to the mix the OpenSource trend...

I think we are in for a fun time. Long time ago, language design was very cool. Then came C++ and it seemed we were all going to be forced to use it but the Java language proved that wrong. Java - the language - itself has remained quite stable. In recent releases it has added some new features but the language is supposed to be fairly stable. The real radical ideas will come from other languages on top of the platform. Not just older languages like Ruby, but also brand new languages, like F3.

I'm looking forward to the next few years!

Comments

• I fear it will lead to massive confusion among end users as things calling themselves JVMs but aren't prolifferate in ever increasing numbers causing in turn major headaches for developers who have to answer ever more questions about applications that don't work despite the user having "Java installed".

  Posted by: jwenting on November 18, 2006 at 12:10 AM

• In fact one thing that caused C++ to not remain top dog was the simple fact that different compilers weren't source level compatible, let alone binary level compatible for shared libraries.

  So you couldn't just create a library and put it out there, you actually had to provide binaries for every conceivable compiler your customers might have.

  That was a major step back, not dissimilar to the OS level incompatibillity that came before it (and is still here to a degree).

  Java is now heading the same way, we'll soon have to provide binaries for dozens of JVMs or loose customers, just like the software makers of the 1980s.
  

  Posted by: jwenting on November 18, 2006 at 12:13 AM

• >Java is now heading the same way, we'll soon have to provide binaries for dozens of JVMs

  Well that is one thing Sun has said it will try very hard to avoid. For one thing, applications and VMs won`t be able to call themselves "Java" if they don't comply with the standard.
  More on topic; the aspect of multiple programming languages running on one VM a la .NET is something to be welcomed, as the developer will have the option of choosing the best language for the job or even combining them for the best results.

  Posted by: oakidoaki on November 20, 2006 at 02:55 AM

• > by Sacha Labourey

  100% Agree. It's like Linux distros. You may choose. :)
  

  Posted by: mblua on November 20, 2006 at 07:03 AM

• Sorry, Here i post again...

  
  ---------------

  As suggested for a long time by JCP members, SUN will use the strong value of “Java” trademark/brand to protect the ecosystem from incompatible implementations (only those that have fully passed the TCK will be allowed to use the “Java” branding/trademark - the FOSS project is named “Open JDK”). That is a simple, clean and efficient solution. This also means it wouldn’t be possible to release a broken “Unbreakable Java” JVM, not that anybody would want to do something that smart though… ;)

  
  by Sacha Labourey

  ---------------

  
  100% Agree. It's like Linux distros. You may choose. :)
  

  Posted by: mblua on November 20, 2006 at 07:05 AM

• I just read your blog in the Java.net forum. I am enthusiastic about your excitement of the next generation of development platforms. We are an IBM shop, working with large scale WS Portal Applications, based out of NYC. Are you interested in working with our company on some contracts or as a permanent employee? We are looking for a strong team lead to join our team.

  Best regards,

  Richard Celic
  Resource and Recruiting Director
  E2 Consulting Group

  rcelic@e2cg.com
  www.e2cg.com

  Posted by: e2 on November 27, 2006 at 08:38 AM

• That is a simple, clean and efficient solution. This also means it wouldn’t be possible to release a broken “Unbreakable Java” JVM, not that anybody would want to do something that smart though… ;)

  Posted by: markovich on October 07, 2007 at 02:58 AM

This work is licensed under a Creative Commons License.