Reasons to open source WebObjects?

Howdy All,

Ok, we've seen a few reasons (and some discussion) of why not to open 
source WebObjects.  So now, let's consider reasons to open source 
WebObjects.

And, to be clear, by this I don't mean just Apple dumping WO as an open 
source project.  I mean them making it open source but playing a 
significant role in its future development etc.

1.  To remove (probably) the number one reason companies are unwilling 
to go with WebObjects - they are worried about its proprietary nature 
and its future.

2.  To enable more developers to get easy access to WebObjects 
(although there already is a trial version) and use it on simple Web 
applications.

3.  To enable the WebObjects community to work on bugs and problems 
that are not high on Apple's priority list (for any of a number of 
reasons).

4.  To allow better integration of Project WONDER and other open-source 
and third-party additions and modifications to WebObjects.

5.  To increase the chances that the amazing technology that is 
DirectToWeb, DirectToJavaClient, and DirectToWebServices gets 
recognised and developed further.

Others?

Of course, none of this will (directly or even indirectly ) result in 
Apple hardware sales, so I'm not sure what is in it for Apple.  That 
said, they do currently support cross-platform Java.

The primary benefit to Apple would be for them to have a wider 
community of developers working on WebObjects (so its less effort for 
them to maintain and improve it for their own use).

Others?

Cheers,
Ashley.

--
Ashley Aitken
Perth, Western Australia
mrhatken at mac dot com
Skype Name: MrHatken (GMT + 8 Hours!)