Ted Leung on the air
Ted Leung on the air: Open Source, Java, Python, and ...
Mon, 15 Sep 2003
Embrace and Extend
Anne Thomas Manes is proposing Jakarta for Mono. Her objective, which I agree with is:
a pretty decent, totally open, multi-platform application environment with no IP-encumbrances from either Microsoft or Sun.
Her proposal:
So this is my idea: we start a set of open source projects that essentially duplicate Jakarta (and other Java projects) for Mono. We start with a servlet-like system for C# (Sharplets?). It needs to be sufficiently different from the Java Servlet API - because servlets are Sun proprietary technology. But then we build on the Sharplets foundation: things like Struts, Cocoon, Log4C#, C#Unit, etc.
Fortunately, nobody stood around waiting for someone to have this idea, and a number of busy developers have already started porting Jakarta projects. Here are some that are already done. There's also a port of JUnit.

So the next step, rather than the first step, is to do something like servlets.

However, I think that Jakarta for Mono is a bad idea. Here's what I mean. Jakarta is not the only source of good open source Java stuff. If we are going to build a multi-platform application environment, let's also learn from the mistakes that have been made along the way. Let's take WebWork or Tapestry instead of Struts. Let's take Velocity over JSP. And let's definitely not take EJB. This is bigger than Jakarta. Much bigger.

As I pointed out in February, there's a lot of open source stuff out there that is better than what the platform vendors have done. A new, not-dependent on Microsoft CLI should take advantage of every lesson that Java and .NET people have learned about building managed systems. The only piece that really matters is the CLI. Would it be nice to be compatible with .NET? Sure. Is Microsoft going to allow it? Who knows? We don't need Microsoft's permission to build something based on all the lessons we've learned since 1996. And we don't need to be compatible with them because we're not compatible now. This is about open source going forward. If Mono is about keeping up with .Net, then its about as interesting as the ASF trying to keep up with J2EE -- not very.

The one troubling piece is the licensing. It may be hard to attract people to write and use code developed on Mono because of the GPL. This may turn out to be more of a problem than Microsoft. If people don't have any option to make money writing Mono apps, then things could get tough. And yes, we should be thinking about Mono desktop apps (If you don't know what Nat Friedman did with dashboard, go find out -- mind the dates in July). Mono is on Windows, Linux, and (soon) MacOS X. There's a group working on SWT bindings to Mono, and Eclipse has already shown that you can do cross platform GUI apps on those three platforms.

Noel Bergman wrote in to say that he'd like to see Mono relicensed to the ASF. I don't know if that's really that important or not. The license may be, but the ASF may not be. Hey, I'm an ASF member too, and I'd love to see Mono come to the ASF. But it's not a prerequisite for success.

Simon Phipps commented with a post titled An Open Spirit:

What we learn from each of these forays into openness is that it doesn't matter how sound the vehicle being used to express the apparent 'openness' is (ECMA for C#, Open Group for DCOM, partenr community for NT), what ultimately matters is the open spirit of the originator. If their intent and method is essentially open, the process bugs get fixed along the way and more and more becomes open.
Unfortunately, for Simon, he's throwing rocks in a glass house. Sun is the company that said they would standardize Java in ECMA and then backed out. Sun is the company that the ASF has had to beat repeatedly in order to fix the "process bugs". We still don't have an open source JVM. Until that changes, Java is not open. When people have to pay money to get certification, that's not open.

The open source community as a whole needs to start going forward because we are running out of good stuff to copy. In order to do that, we need the entire stack to be open. Let me give you one example: There's a lot of buzz going on right now about "dynamic languages". People are starting to realize that there might be some useful stuff in these languages. The problem is that they perform poorly on the JVM (and the CLI). Sun is not interested in solving this problem. Microsoft is. And even if Microsoft isn't or doesn't, it doesn't matter, because the problem can be solved by modifications to Mono.

Let's give up the dream of .NET compatiblity. And J2EE compatibility. Let's take the CLI and chart our own course.

[01:41] | [computers/open_source] | # | TB | F | G | 9 Comments | Other blogs commenting on this post
My comment with regard to Mono being re-licensed to the ASF was in context of Anne Thomas Manes proposing Jakarta for Mono.  She was the one who suggested the place.  I qualified my comment by saying that it would be good to have the entire stack under a suitable license.  The VM doesn't have to be at the ASF or with that license, but as you noted, the key issue is the nature of whichever license.  You want a license that permits participation from both Open Source developers and closed source vendors on a common Open Source platform.

A high quality, Open Source, VM would be nice.  Perhaps one that learned from the JVM, CLI, and other VMs, and provided compatibility with the best features of each.  And there are lessons to be learned from existing frameworks.

But there is such a thing as critical mass.  Why does creating new de jure Open Standards mean abandoning the critical mass we've developed in de facto ones?  Would it really be easier to develop a new utopian platform than to morph an existing one?

Anytime one is talking about certification, the underlying issue is interoperability.  If interoperability didn't matter, one wouldn't care about certification.  In terms of charging fees for certified compatibility with Open Standards, check out the pricing from theopengroup.org, or other standards bodies.  Would I like Java certification for free?  Of course.  AIUI, once an certified J2EE stack exists from the ASF, anyone can use it for free as a certified J2EE, provided it is not changed in such manner as to compel re-certification.

If you are going to build a critical mass around something, one question is with whom do you want to work.  Microsoft is establishing a proprietary system under the pretense of an Open Standard.  Sun has a relatively Open System under the guise of proprietary ownership.  Is the JCP perfect?  Certainly not.  Has it improved?  Seems so.  At the moment, it appears that working to resolve the JCP's problems with Sun and others would be more managable than attempting the classic blunder of trying to skirt technological entrapment.
Posted by
Noel J. Bergman at Mon Sep 15 11:02:30 2003








If you believe that Sun knows best, then keep right on with Java and EJB.

It would be convenient to write off my statements as some kind of blind faith, but your comments about Sun and ECMA standardization certainly looked shallow to me and motivated me to spend the time to post a comment.  I am more interested in understanding and spreading good ideas than expressing opinions. (Did I write anything about EJBs? ;^)



I think your Sept. 16 posting, which spelled out your desire to fork open source, clarifies your position.  Apparently, you have yet to experience the downside of a proliferation of incompatible  variants.



Regarding Dylan, I do know about it.  I was working on "Trusty Scheme", a secure version of Scheme at Autodesk when Dylan (Scheme without continuations and parens) was being developed (1990-1992).  Sun was also building a Scheme environment at that time too.  As much as I liked Trusty Scheme, which was interpreted, I recognized that Oak/Java blew it away in performance by orders of magnitude with the JIT compiler and the verifier. 



See
http://www.eros-os.org/ for the further evolution of the capability security of Trusty Scheme in the EROS OS.  Java borrowed heavily from Self  http://research.sun.com/self/language.html which evolved from Smalltalk.



I agree that, in the long run, as "Moore's Law" continues, dynamic languages (and languages with more dynamic features) will get more of the programming pie because execution efficiency is  increasingly less important than saving programmer time.
Posted by Paul Baclace at Tue Sep 16 21:51:20 2003


If you believe that Sun knows best, then keep right on with Java and EJB.

It would be convenient to write off my statements as some kind of blind faith, but your comments about Sun and ECMA standardization certainly looked shallow to me and motivated me to spend the time to post a comment.  I am more interested in understanding and spreading good ideas than expressing opinions. (Did I write anything about EJBs? ;^)



I think your Sept. 16 posting, which spelled out your desire to fork open source, clarifies your position.  Apparently, you have yet to experience the downside of a proliferation of incompatible  variants.



Regarding Dylan, I do know about it.  I was working on "Trusty Scheme", a secure version of Scheme at Autodesk when Dylan (Scheme without continuations and parens) was being developed (1990-1992).  Sun was also building a Scheme environment at that time too.  As much as I liked Trusty Scheme, which was interpreted, I recognized that Oak/Java blew it away in performance by orders of magnitude with the JIT compiler and the verifier. 



See
http://www.eros-os.org/ for the further evolution of the capability security of Trusty Scheme in the EROS OS.  Java borrowed heavily from Self  http://research.sun.com/self/language.html which evolved from Smalltalk.



I agree that, in the long run, as "Moore's Law" continues, dynamic languages (and languages with more dynamic features) will get more of the programming pie because execution efficiency is  increasingly less important than saving programmer time.
Posted by Paul Baclace at Tue Sep 16 22:32:44 2003

You can subscribe to an RSS feed of the comments for this blog: RSS Feed for comments

Add a comment here:

You can use some HTML tags in the comment text:
To insert a URI, just type it -- no need to write an anchor tag.
Allowable html tags are: <a href>, <em>, <i>, <b>, <blockquote>, <br/>, <p>, <code>, <pre>, <cite>, <sub> and <sup>.

You can also use some Wiki style:
URI => [uri title]
<em> => _emphasized text_
<b> => *bold text*
Ordered list => consecutive lines starting spaces and an asterisk

Name:


E-mail:


URL:


Comment:


Remember my info?


twl JPG

About

Ted Leung FOAF Explorer

I work at the Open Source Applications Foundation (OSAF).
The opinions expressed here are entirely my own, not those of my employer.

Creative Commons License
This work is licensed under a Creative Commons License.

Now available!
Professional XML Development with Apache Tools : Xerces, Xalan, FOP, Cocoon, Axis, Xindice
Technorati Profile
PGP Key Fingerprint
My del.icio.us Bookmarks
My Flickr Photos


Syndicate
RSS 2.0 xml GIF
Comments (RSS 2.0) xml GIF
Atom 0.3 feed
Feedburner'ed RSS feed

< September 2003 >
SuMoTuWeThFrSa
  1 2 3 4 5 6
7 8 910111213
14151617181920
21222324252627
282930    

Archives
2006
2005
2004
2003

Articles
Macintosh Tips and Tricks

Search
Lucene
Blogs nearby
geourl PNG

Categories
/ (1567)
  books/ (33)
  computers/ (62)
    hardware/ (15)
    internet/ (58)
      mail/ (11)
      microcontent/ (58)
      weblogs/ (174)
        pyblosxom/ (36)
      www/ (25)
    open_source/ (145)
      asf/ (53)
      osaf/ (32)
        chandler/ (35)
        cosmo/ (1)
    operating_systems/ (16)
      linux/ (9)
        debian/ (15)
        ubuntu/ (2)
      macosx/ (101)
        tips/ (25)
      windows_xp/ (4)
    programming/ (156)
      clr/ (1)
      dotnet/ (13)
      java/ (71)
        eclipse/ (22)
      lisp/ (34)
      python/ (86)
      smalltalk/ (4)
      xml/ (18)
    research/ (1)
    security/ (4)
    wireless/ (1)
  culture/ (10)
    film/ (8)
    music/ (6)
  education/ (13)
  family/ (17)
  gadgets/ (24)
  misc/ (47)
  people/ (18)
  photography/ (25)
    pictures/ (12)
  places/ (3)
    us/ (0)
      wa/ (2)
        bainbridge_island/ (17)
        seattle/ (13)
  skating/ (6)
  society/ (20)



[Valid RSS]

del.icio.us linkblog

www.flickr.com

Blogroll

java.blogs
Listed on BlogShares

Locations of visitors to this page
Where are visitors to this page?


pyblosxom GIF