Bill de hÓra: JVM ascendent

Image Roll

www.flickr.com

Archives

July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
January 2000

« Understanding REST | Main | XP: discipline is not enough »

JVM ascendent

October 28, 2003 | co.comments icon co.mments

Brian McCallister

What's growing? Ruby, Python, Java as platform (not the language). The scripting languages need no explanation. The Java as platform might: the most real innovation happening in Java is not happening in the Java language, but in other languages that run on a JVM.

My thoughts on this: The Java Ceiling. See also: Groovy (but Jython is there already).

October 28, 2003 11:32 PM

Comments

Brian McCallister

(October 29, 2003 02:33 PM #)

I've been playing with Groovy since James sent me an email about it based on that blog article. I like it a lot. You are absolutely correct about this being an example of the JVM ascendent, I think.

Isaac

(October 29, 2003 09:05 PM #)

"To really do that, you need a language that lets you change the software while it's running. In the past, this need was not a business need - it was limited to a minority using Lisp Machines and Smalltalk, or experimental scripting environments. Only the mainframe needed to stay up 24x7 and businesses requirements tended to be a tad more stable."

Actually, in the past this was a business need too! That "minority" were using Smalltalk to build 24x7 enterprise systems that could be hot-fixed. Things change quickly in investment banks.

Seems to have been a pretty important requirement in Ericssons design of Erlang www.erlang.se

Trackback Pings

TrackBack URL for this entry:
http://www.dehora.net/mt/mt-tb.cgi/1111