Re: WO 5.3...confusion
Re: WO 5.3...confusion
- Subject: Re: WO 5.3...confusion
- From: Doug McClure <email@hidden>
- Date: Sat, 11 Jun 2005 10:54:31 -0400
On 6/8/05, Ricardo Parada <email@hidden> wrote:
>
> As far as deployment, WO is a java-based library. And the source to
> WebObjects adaptor for Apache is provided.
> And Apple won't stop you from deploying on a non-Apple server.
While very true, one has take into consideration the history of WO.
Initially, WO was part of the grander EOF strategy available for
YellowBox / Openstep. Then Java was chosen in favor of ObjC. That
was the beginning of the end for ObjC WO. Writing client-server EOF
apps was dropped as a supported option. Then ObjC was dropped as a
supported option for WO. Development on Windows wasn't exactly
dropped, but nearly effectively EOLed. Now development or deployment
on anything other than OS X is no longer a supported option.
It is not difficult to imagine that in the near future, Apple will
change WO in such a way that it can't be deployed on anything other
than OS X. History tells us while WO may experience some changes for
the better over time, there will also be changes that will reduce its
appeal to a wider audience.
And while you might say Apple would never do that, WebApps need to be
in Java, but what if they abandoned EOF to use CoreData instead using
the dreaded ObjC-Java bridge, so we could write GUI client-server apps
and use the same business objects for WO too?
In the end it all boils down to the fact tha Apple continues to not
give us any information about the direction of WO, other than just
miniscule glimpses of information once in a blue moon, or some vague
information hidden behind NDA stuff at WWDC. We have to gleam their
plans from what they actually do.
For example, Apple adding the Collection interface to NSArray /
NSDictionary / NSSet (about time!) is great, but what does it MEAN?
Does it mean Apple finally understands that as great as the Foundation
stuff is, that you need to play in the Java world, and if your stuff
at least works like Java stuff your re-inventing, non-WO Java people
will be more comfortable using it? Does it mean that Apple is going
to migrate all of their APIs to using the Collection interface so we
don't have to deal with converting from one data storage class to
another? Is Apple going to ditch their Foundation classes that
duplicate Java ones? Or does it just mean some WO developer was able
to check off a bug that I'm sure a few people filed with Apple. We
have no idea. We don't know were they are going with this, we can't
make plans.
If you can't make plans with one thing, you find a way to make a plan
with something else. Apple just showed us the biggest example of that
with the move to Intel. And they force us to do similar for WO.
-d
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden