Hi!
One thing that Apple has cleared showed it's clients is that they
don't specially care about backward compatibility beyond a certain
point. If they think there's a clear advantage in doing something,
they will do it, like moving to Apache 2, etc. So I don't think that
backward compatibility with Apple installed systems is the reason for
WO development being so slow. Keep in mind that Apache 2 will only be
the default web server on Leopard Server that didn't come out yet.
Tiger Server has Apache 2, but the default and recommended server is
Apache 1. So this is not a WO-specific issue. Looks like Apple didn't
trust Apache 2 until a few months ago.
About open-sourcing, I have very mixed feeling about open-source
in general. I prefer to have few people working slowly in a certain
product, but keeping a high level of quality, than having everyone
(including people that don't really understand the framework)
committing code. I think that, most of the times, open source leads
to lower quality, unless the project leaders have a very strong hand.
We are lucky in the WO Community because guys like Mike and Anjo know
a lot about WO and are very good coders, but the majority of the
other projects are not that lucky. (Of course, one could say exactly
the same about commercial apps, that's why I have mixed feelings!)
Also, I believe the fact that Apple uses WO internally is the
reason why it still exists, why is it so stable, and why is Apple
supporting the WO open-source community.
Yours
Miguel Arroz
On 2007/07/05, at 08:32, Jean Pierre Malrieu wrote:
This post ought to be sent to WO-talk, but I can't post there right
now.
A lot of people say that because Apple is using WO internally, we
need not worry about WO death.
I agree with that, but I am starting to wonder whether Apple using
WO is a good thing for WO...
If Apple had chosen another technology for iTunes store, the Apple
Store and .mac, WO would no longer be a matter of competitive
advantage for Apple and therefore, Apple could open source it.
WO would have evolved much faster if Apple was not using it. What
is the reason for sticking with apache 1.3 and java 1.4 for so long
if not Apple internal apps? Isn't WO evolving slowly because Apple
needs to keep it compatible with old code it uses in its internal
applications, and old deployment platforms?
What prevent Apple from publishing clear roadmaps for WO? The fact
that the future of the product depends on Apple's internal needs,
which can vary a lot, and that Apple does not want to disclose.
Overall, I am not sure that Apple using WO internally is a very
good thing for WO.
JPM
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/arroz%
40guiamac.com
This email sent to [EMAIL PROTECTED]
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
